python-poetry / python-poetry/poetry
Add 'dev' as version bump rule for developmental releases.
Open
Nobody has claimed this yet.
kind/feature
status/triage
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 2.5k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 30
Description
- I have searched the issues of this repo and believe that this is not a duplicate.
- I have searched the FAQ and general documentation and believe that my question is not already covered.
Feature Request
I would like to use poetry version dev to automatically increment my versions according to the PEP-440 rules for developmental releases.
Expected behaviour:
| rule | before | after |
|---|---|---|
| dev | 1.0.2 | 1.0.2.dev0 |
| dev | 1.0.2.dev0 | 1.0.2.dev1 |
| dev | 1.0.2a0 | 1.0.2a0.dev0 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the implementation of the poetry version command and its version-bump rules, then review how PEP 440 developmental versions are handled. Use the three examples in the issue as acceptance cases: 1.0.2 becomes 1.0.2.dev0, subsequent development versions increment, and pre-releases gain a .dev0 suffix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100