Enable poetry version postrelease to create version numbers like 1.0.0post1

[dfm-vmd]

Issue Kind

Brand new capability

Description

PEP440 allows for postrelease version numbers like 1.0.2post1. I'd like to enable to poetry CLI to automate creating postrelease versions. The command poetry version postrelease should convert the following version numbers in pyproject.toml.

original version	after running poetry version postrelease
0.0.1	0.0.1post0
0.1.0	0.1.0post0
1.0.0	1.0.0post0
1.0.0post0	1.0.0post1
1.0.0a0	1.0.0a0post0

PEP440 documentation:
https://peps.python.org/pep-0440/#post-releases

Impact

I'd like to use poetry to maintain and automate my version numbers for a work project. I'd like to use the postrelease spec to enable hotfixes on old versions. I.e. if I am running v1.0.0 in a production setting, and actively contributing to a v1.0.1, I'd like to be able to create hotfixes or updates to v1.0.0 (deployed under v1.0.0post1) without cross-pollenation of changes with v1.0.1.

Workarounds

Manually update version in pyproject.toml

[dimbleby]

what you propose to do is "strongly discouraged" - https://packaging.python.org/en/latest/specifications/version-specifiers/#post-releases

The use of post-releases to publish maintenance releases containing actual bug fixes is strongly discouraged.

I do not think that encouraging this mis-use of post-releases would make the world a better place

[dfm-vmd]

I'm not trying to cast any judgement on the spec, just trying to fully enable it.