ci(release): prepend highlights from release-notes/<tag>.md#62
Merged
Conversation
The auto-generated PR-list changelog never includes a Highlights section, and manually editing the GitHub draft release body only updates the release page — it does not write back into latest.json's notes field, so the in-app updater dialog stays empty of highlights. Have the Generate changelog step look for a hand-written .github/release-notes/<tag>.md and prepend its contents to the body before writing $GITHUB_OUTPUT. The same body feeds both the draft release (gh api) and tauri-action's releaseBody, so highlights now appear in both surfaces automatically. File missing or empty (-s test) falls back to existing behavior, so this is a no-op for any release that doesn't author a highlights file. Add a README under .github/release-notes/ documenting the convention and the full release flow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
RealZST
force-pushed
the
ci/release-highlights-from-file
branch
from
fcc7f90 to
d4bf568
Compare
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.
Summary
Make the in-app updater dialog show release Highlights without any manual fix-up after publishing.
Problem:
release.ymlGenerate changelogstep builds the body fromgh api .../generate-notes, which only produces a PR list — no Highlights. Manually editing the GitHub draft body adds them on the release page, but does not write back intolatest.json.notes, so the in-app updater dialog stays Highlights-less. v1.4.0 was patched by hand (gh release download latest.json→ edit →--clobberupload).Fix: Have the changelog step look for
.github/release-notes/<tag>.mdand prepend its contents to the body before writing$GITHUB_OUTPUT. The same body feeds both the draft release (gh api) and tauri-action'sreleaseBody, so Highlights now appear on the release page and inlatest.json.notesautomatically.-stest → file missing or empty falls back to existing behavior, no-op for releases without a highlights file.github/release-notes/README.mddocumenting the convention and the full release flow (including thescripts/bump-version.shstep)Test plan
.github/release-notes/v<tag>.md, runbump-version.sh, commit, tag, pushcurl -L .../latest.json | jq -r .notescontains Highlights🤖 Generated with Claude Code