Bump only updates the first match in a version_file
See original GitHub issueDescription
Since version 2.17.3 cz bump
seems to only update the first match it finds in any given version_file.
Steps to reproduce
- Set up pyprject.toml, in my case I am using commitizen as well as poetry, each of which with a version entry in its setup.
- Run
cz bump
.
Current behavior
Only the first match gets updated.
Desired behavior
All matching lines should be updated it was before version 2.17.3 (<2.17.3).
Environment
- commitizen version: >=2.17.3
- python version: Python 3.8.6
- operating system: Darwin
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Unhelpful error message related to unresolvable python version
Description: When neither python-version or python-version-file is set, and there is no version file matching python-version-file's default ...
Read more >bumpver - PyPI
With the CLI command bumpver , you can search for and update version strings in your project files. It has a flexible pattern...
Read more >Versioning using bumpversion - William Hayes, PhD
The nice thing about it is it makes it easy to update all of the files that might contain your version numbers such...
Read more >c# - Can I automatically increment the file build version when ...
The reason is that all references to such an assembly must be updated each time the referenced assembly is rebuilt due to the...
Read more >Setup version increment and automated release process
You have 2 free member-only stories left this month. ... Bash script to check if VERSION file changed against master:
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I confirm that the issue has been fixed! Great work! Thanks a lot!
@pedrorrivero We’ve just merged #386 . I think it should have fixed it. I’ll close this issue. We could re-open it if it doesn’t solve the problem