Fix CHANGELOG for release that didn't occur#2101
Merged
Merged
Conversation
edmorley
changed the title
colincasey
approved these changes
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The original v345 release (prepared in #2095) never ended up being published (I forgot to run the final
make publishstep), and so was superseded by #2100 - which resulted in two v345 entries being present in CHANGELOG.Longer term we should add a self-check to the prepare release GitHub Actions workflow so that it fails if the changelog is in an inconsistent state. (Though that said, the new release automation triggered on merge of the prepare-release PR would prevent the need to manually run
make publish, and so prevent this issue too.)