nebula-plugins / nebula-plugins/nebula-release-plugin
Prevent Non-Linear Version Incrementing by Default
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
Releasing a version that makes an unexpected jump is often unintended. It would be great if the plugin would prevent such changes by default. It's possible someone could want to do a larger jump (e.g. v8.0.0 to v8.5.0), so there should be a way to opt-out.
Successful examples:
| Last Version on Branch | Next Version |
|---|---|
| 0.0.1 | 0.0.2 |
| 0.0.1 | 0.1.0 |
| 0.0.1 | 1.0.0 |
Failed examples:
| Last Version on Branch | Next Version |
|---|---|
| 0.0.1 | 0.0.12 |
| 0.0.1 | 0.22.0 |
| 0.0.1 | 44.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 the release version calculation and configuration entry points to find where the previous and next versions are compared. Add default rejection for the failed non-linear examples while preserving the successful examples, and provide an opt-out mechanism. Done means the behavior is covered by tests and the opt-out is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100