Automated suggestions for semantic release number
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Description of feature
Since we've started being clearer that we'd like folks to actually follow semantic versioning, and provided some more concrete guidance, it would be helpful if tools already provided some suggestions as to what a release should be.
e.g.:
- Changes to existing parameters since last release (definitely a major release)
- Additional parameters since last release, without changes to existing (maybe a minor version
Details very much up for grabs.
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
No file, test, or entry point is named. Start by reading the linked semantic versioning guidance and then locate the existing release and versioning behavior in the tools package. This issue is done only when the suggestion rules and their expected behavior are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100