influxdata / influxdata/changelog
nextver should error when trying to generate a point release with a feature
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Recently, we tried to use changelog to generate a point release. At the time, v0.87.0 was the most recent release. We wanted to make a release the v0.83.x series, the result being v0.83.1. changelog nextver was returning v0.88.0 as the next version. Upon further investigation, it's because the cherry-picked change to v0.83.x was a feat change, so changelog was rightfully trying to say "This can't be a point release." However, it's still incorrect, because v0.88.0 would end up missing changes that were added between v0.83.0 and v0.87.0, so that release would be wrong.
DOD:
- When running
changelog nextverfor a point release, an error should be returned if a non-fixoriented change is detected.
Contributor guide
No contributing guide indexed for this repository
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 at the changelog nextver command and trace how it selects the next version for a point-release branch. Reproduce the v0.83.x scenario with a non-fix change; done means the command returns an error instead of proposing a version that omits intervening changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100