Say what the release candidate fixes - #24
Merged
Merged
Conversation
The Linux startup crash, the clipped stance row and the alert placement all landed without changelog entries, so release notes generated for 0.4.0 -- and for every candidate resolving to it -- would not have mentioned the fix that stopped the application starting at all on Linux. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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 Linux startup crash, the clipped stance row and the alert placement all merged without changelog entries.
tools/release_notes.pybuilds release notes from the0.4.0entry, and a candidate resolves to the same entry, so without this the notes for rc.3 — and for 0.4.0 itself — would not mention the fix that stopped the app starting at all on Linux.🤖 Generated with Claude Code