codejedi365

Thanks for the error message details. The second error you received I think is because you removed the `ssh-key: ${{ secrets.DEPLOY_KEY }}` from the checkout action. When checkout action occurs...

That's very disappointing. I will have to look into this further as now it should just be only an access token issue for the API. I assume that you did...

Ok great. Please just double check that you have granted the token permissions of `contents: write` and that PSR's log did not issue a warning about a missing or empty...

@JCHacking, Have you tried just setting the `semantic_release.remote.type = "gitea"` and then provided additional configuration such as the domain name and other settings for your environment. I don't have a...

@JCHacking, thanks. I'll have to check it out. You will likely get an opportunity to test it before I do so let me know if it ends up working.

No update, still in backlog

I wish you had actually filled out the template. It's there for a reason. Your config would be helpful and a commit tree which was requested. The fact is I...

I don't need the whole project configuration just the semantic release part, but I understand. [Conventional Commit Parser - Regular Expression component](https://github.com/python-semantic-release/python-semantic-release/blob/master/src/semantic_release/commit_parser/conventional/parser.py#L139) [`Conventional Commit Parser - parse()`](https://github.com/python-semantic-release/python-semantic-release/blob/master/src/semantic_release/commit_parser/conventional/parser.py#L294)

> What settings do I need to group my change log release notes by the actual release version and not the commit date? I don't know because that is not...

Thanks for the note. Its not worth fixing since docs are not part of the actual wheel install and we don't use `uv` for development installs