Guessing the next release with prereleases is not honored
- Dominant language
- Go
- Stars
- 65
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Given a changelog with no patch fixes and a previous release that has a prerelease indicator, chronicle should not bump the patch version:
```
./.tmp/chronicle -vvv -n --version-file VERSION
Changelog
## v0.14.1 https://github.com/anchore/grype-db/tree/v0.14.1 (2023-02-16)
Full Changelog https://github.com/anchore/grype-db/compare/v0.14.0-rc1...v0.14.1
```
Chronicle should either:
- default to the next release candidate: v0.14.0-rc2
- or default to the final release: v0.14.0
Contributor guide
Research direction
Reproduce the behavior with the shown ./.tmp/chronicle command, the changelog output, and VERSION. Trace the release-version inference logic and determine whether the expected result is v0.14.0-rc2 or v0.14.0; done means prerelease history no longer causes an unintended patch bump.
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