Automatically bump version during template update
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
When a new Template gets released, the pipeline semver should match the tools semver bump.
So for example:
| Template Update | Pipeline Version |
|---|---|
| 2.10.0 => 3.0.0 | 3.16.0 => 4.0.0 |
| 3.0.0 => 3.1.0 | 3.16.1 => 3.17.0 |
| 3.0.0 => 3.0.1 | 3.16.1 => 3.16.2 |
We should automate this bumping during the PRs somehow and nudge the developers to cut a release if it's past 1.0.0
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 tracing how template releases and pipeline version bumps are currently performed in the repository and its release automation. Define the desired semver mapping and the mechanism for nudging developers to cut a release; done means the bump is automated during pull requests and the post-1.0.0 release warning is covered.
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