"semantic-release version" not updating pyproject.toml or git tag
See original GitHub issueThe problem
I’m using PSR (v7.29.2) with poetry and when running semantic-release version
I receive the following output:
Creating new version
Current version: 0.1.0, Current release version: 0.2.0
However, the pyproject.toml file still has version = "0.1.0"
and no new tags are generated. Per the docs, this should “Figure out the new version number, update and commit it, and create a tag.”, but seemingly nothing is happening except the new version determination. No warnings or errors are observed using -v WARNING or -v ERROR, respectively.
Expected behavior
I expected the version number to be updated to 0.2.0
in pyproject.toml, a new tag to be generated, and the change to be committed.
Also, per https://py-pkgs.org/07-releasing-versioning I expected to the following output:
Creating new version
Current version: 0.1.0
Bumping with a minor version to 0.2.0
Maybe that is no longer expected output, but at least expecting notification of bump.
Additional context
Issue Analytics
- State:
- Created a year ago
- Reactions:5
- Comments:10 (3 by maintainers)
Top GitHub Comments
Hello, we’re having issues when adding new projects that already have a non 0.0.0 version but didn’t create commits with the version number. get_current_release_version_by_commits returns 0.0.0
We get this in the logs:
I don’t have time to debug further so we’re rolling back to 7.28.1 for now.
@bheijden Your explanation seems correct. I have a commit with
pip: bump types-requests from 2.28.0 to 2.28.2 (#23)
from dependabot. It is indeed the2.28.0
thatsemantic-release publish -v debug --noop
picks up:I am using
python-semantic-release 7.29.6
.Downgrading to
7.28.0
allows the operation to proceed as expected.