-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add --next-phase command to poetry version #8089
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since there has been only positive feedback in #1959 so far, I think we can proceed.
The PR looks good in general, I just like to have another test that passes the command line parameter.
Aligned the documentation table and added a new test with the command line parameter as requested @radoering |
Deploy preview for website ready! ✅ Preview Built with commit eca37f6. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Pull Request Check List
Resolves: #1959
This PR include a new flag
--next-phase
for thepoetry version
command, which will only have impact when using theprerelease
argument.The behaviour of
--next-phase
is to increment the phase of the current version eg:poetry version prerelease --next-phase
poetry version prerelease
poetry version prerelease --next-phase
poetry version prerelease
poetry version prerelease --next-phase
From my perspective this is the most correct way to handle the phases of the prereleases as defined by
poetry-core
version module.