Skip to content

build: base prerelease notes on the channel's previous tag - #545

Merged
AkibaAT merged 1 commit into
mainfrom
fix/prerelease-notes-base
Nov 9, 2026
Merged

AkibaAT merged 1 commit into
mainfrom
fix/prerelease-notes-base

Conversation

@AkibaAT

@AkibaAT AkibaAT commented Nov 9, 2026

Copy link
Copy Markdown
Collaborator

The Problem/Issue/Bug:

GitHub's generated release notes compare against the newest release of any kind. 1.3.0-alpha5 was created right after 1.2.11-beta1, so its notes compared 1.2.11-beta1...1.3.0-alpha5, a diff between two unrelated lines.

How this PR Solves the Problem:

The version job also outputs previous: the highest existing tag of the same channel and target version (1.3.0-alpha5 for the next alpha), or the latest stable release when it is the first one. The release step passes it as previous_tag.

Manual Testing Instructions:

actionlint passes. Dry-run of the version step against this repository: alpha gives 1.3.0-alpha6 with base 1.3.0-alpha5, beta gives 1.2.11-beta2 with base 1.2.11-beta1.

The existing 1.3.0-alpha5 release notes were regenerated against 1.2.10 by hand.

Related Issue Link(s):

Follow-up to #544, refs #538

Generated notes compared against the newest release of any kind, so an
alpha listed its changes relative to a beta. They now compare against the
previous tag of the same channel and target version, or the latest stable
release for the first one.
@AkibaAT
AkibaAT merged commit 1c54431 into main Nov 9, 2026
9 of 11 checks passed
@AkibaAT
AkibaAT deleted the fix/prerelease-notes-base branch November 9, 2026 01:51
@github-project-automation github-project-automation Bot moved this from New to Done in Development Nov 9, 2026
@sonarqubecloud

sonarqubecloud Bot commented Nov 9, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant