poetry version should optionally apply an SCM tag as well
See original GitHub issue- I have searched the issues of this repo and believe that this is not a duplicate.
- I have searched the documentation and believe that my question is not covered.
Feature Request
My current workflow uses bumpversion
to search and replace all the occurrences of the version.
bumpversion also creates a git tag for us.
It’d be great to have this feature in poetry as well.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:33
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Dependency specification | Documentation
Dependency specification Dependencies for a project can be specified in various forms, which depend on the type of the dependency and on the...
Read more >Why you should use Poetry instead of Pip or Conda for ...
Poetry : Poetry is a newer dependency management tool that is gaining visibility and popularity for Python users. The use of pyproject.toml and ......
Read more >Poetry: Finally an all-in-one tool to manage Python packages
To study poetry, we will create a simple project poet using the new command. > poetry new poet. The tree structure of the...
Read more >Versioning - Renovate Docs
Renovate interprets versions correctly out-of-the-box most of the time. ... Docker image authors can use whatever tag they want, it's a "wild west"....
Read more >package
You can run ./pants package :: to build all artifacts in your project. Pants will filter to only the relevant targets.. Benefit of...
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 Free
Top 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
Thats true, of course, but the idea here is to gain a single point of truth for the version. Its basically error prone to run poetry version, commit the changes and set a tag (It does not really make sense the other way round, since this way the version number in the repository is not aligned to the tag). So I have to type or stack commands in three commands.
With yarn you run yarn version, which commits the changes and set a tag - And you are done.
If poetry rejects to provide this simple functionality, external tools are required to achieve the same workflow and we miss a chance to gain a really well integrated package manager from my point of view. Please consider to reopen this.
At the very least it should be optional as an extension.