-
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
Extend poetry version xxx
commands to support -beta.#
and -rc.#
#1959
Comments
Perhaps adding an options flag poetry/poetry/console/commands/version.py Lines 14 to 21 in affe32d
Where poetry/poetry/semver/version.py Line 300 in affe32d
|
will it ever be made? |
@python-poetry/triage |
A problem is that the library import semantic_version
semantic_version.Version("0.19.0a1") Results in
|
This is still an issue... would like to be able to iterate on prepatch versions of a patch without overwriting previous alpha versions. Bumping the patch version isn't what we want because the patch hasn't been released yet. |
To those who are still waiting this feature: Can you please have a look whether #8089 satisfies your use cases? It's different from the original proposal in this issue, but seems to offer similar functionality from my perspective. (Since I'm not using |
looks awesome |
It's works for my usecase requiring an RC version. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Feature Request
poetry version prepatch
(or prerelease, etc.) is great for incrementing the version from1.2.3
to1.2.4-alpha.0
, and then to1.2.4-alpha.1
, etc. but this is the extent of the functionality.https://python-poetry.org/docs/cli/#version
It would be great if we could add a few other commands to allow for pre-release name patterns. Adding
alpha
,beta
, andrc
would make sense as the other available commands to support other pre-release versions. This could work as:This would adhere to the pre-release precedence order described here:
https://semver.org/#spec-item-11
Thanks for considering!
The text was updated successfully, but these errors were encountered: