Skip to content

Start the release notes from the previous release of the same series - #5

Merged
vramperez merged 1 commit into
mainfrom
release-notes-from-previous-version
Nov 10, 2026
Merged

vramperez merged 1 commit into
mainfrom
release-notes-from-previous-version

Conversation

@vramperez

Copy link
Copy Markdown
Contributor

Summary

gh release create --generate-notes starts the notes from the latest release of the repository. In a repository that also releases charts, that is often a chart release (<chart>-X.Y.Z): the pre-release 1.0.1-PRE-45 of decentralized-iam listed the pull requests since decentralized-iam-2.1.29, which have nothing to do with it.

github-release.sh now passes --notes-start-tag with the previous release of the same series: the highest <prefix>X.Y.Z tag below the version, where the prefix is whatever precedes the version number (v in v1.2.3, nothing in 1.2.3). Tags of other series, pre-releases and moving major tags are ignored. When there is no previous release, nothing is passed and GitHub picks the start, as before.

Not a breaking change.

Testing

  • bats: the start for a pre-release (1.0.1-PRE-45 → 1.0.0, ignoring a chart tag), for a release compared numerically (11.39.1 → 11.39.0, not 11.9.0), for a prefixed version (v1.2.1 → v1.2.0, ignoring v1), and without a previous release.
  • shellcheck and actionlint.

gh release create --generate-notes starts the notes from the latest release of the repository. In a repository that also releases charts, that is often a chart release (<chart>-X.Y.Z), so the notes of 1.0.1-PRE-45 listed the pull requests since decentralized-iam-2.1.29. github-release.sh now passes --notes-start-tag with the highest <prefix>X.Y.Z tag below the version, and leaves it out when there is none.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vramperez
vramperez merged commit d994ccc into main Nov 10, 2026
7 of 8 checks passed
@vramperez
vramperez deleted the release-notes-from-previous-version branch November 10, 2026 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants