Repository navigation
Fork release: real release notes - #10
Merged
Merged
Conversation
The notes said only which commits were built. They now list upstream's notes for every nightly since the previous fork build, then the fork's pull requests, so the update popup and the release page show what changed. The commits move into a hidden comment that the skip check, the watcher and the watchdog read. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
added
vouch:trusted
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
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 fork's release notes only said which commits were built ("Fork: …", "Upstream: …", "builds of upstream … with the fork's features"). The update popup and the release page should show what actually changed.
fork/release-notes.shwrites upstream's notes for every nightly since the previous fork build (oldest first, because the app shows a body's last entries first), then the fork's own pull requests (GitHub's generate-notes between the two fork tags).<!-- fork-release fork=… upstream=… upstream-tag=… -->comment. The skip check, the watchdog and the watcher read that instead of the visible text.Tested against real releases, including the app's own parser (
normalizeDesktopUpdateReleaseNotes).🤖 Generated with Claude Code