fix(release): auto-publish + generate notes in CI, refresh in-app changelog#64
Merged
Conversation
…changelog Two release gaps surfaced shipping v0.1.7: - release.yml built a DRAFT release (electron-builder --publish always) but never published it or wrote notes — every release needed a manual publish and shipped with an empty GitHub body. New 'finalize' job (needs: build, tag-push only) generates 'What's Changed' notes from merged PRs, prepends the tag annotation summary, and flips the draft to a published latest. - the in-app What's-New changelog (packages/shell/changelog/changelog.json) still had only the 0.0.1 'Pre-alpha development build' entry — it was never updated across 0.1.4..0.1.7. Adds the 0.1.7 entry (v2 block format). The in-app changelog is bundled at build time, so it MUST be committed before the release is tagged — the /release-notes skill makes that a pre-tag step. Co-Authored-By: Claude Fable 5 <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.
Two release gaps surfaced while shipping v0.1.7.
1. CI never published the release or wrote notes
release.yml's singlebuildjob runselectron-builder --publish always, which creates a draft release and uploads every artifact — but never publishes it and never writes a body. So every release had to be published by hand (I published v0.1.7 manually) and shipped with empty release notes (v0.1.6 too).New
finalizejob (needs: build, tag-push only): generates "What's Changed" notes from the merged PRs via the GitHub API, prepends the tag annotation subject as a one-line summary, and flips the draft → published--latest. Aworkflow_dispatchdry-run still publishes nothing.2. In-app "What's New" showed pre-alpha content
packages/shell/changelog/changelog.jsonstill had only the0.0.1 — Pre-alpha development buildentry (May 23); it was never updated across 0.1.4–0.1.7, so the in-app changelog popover showed stale pre-alpha copy. Adds the 0.1.7 entry in the v2 block format (parses + passes the changelog/gating tests)./release-notesskill (harness) makes updating it a pre-tag step, alongside the site downloads entry.Verified:
bun run lintclean; changelog parser + gating tests green (38).🤖 Generated with Claude Code