Repository navigation
release: fold the entries merged after the 0.3.0 prepare into 0.3.0 - #392
Merged
Merged
Conversation
The tag cannot point at the #339 merge: `pnpm audit --prod` there reports the next advisories #389 and #390 patched, and the release's Docker job runs that audit. Tagging current main ships #385, #387, #388, #389, #390 and #391 in 0.3.0, so their entries move from Unreleased into the matching 0.3.0 subsections, the heading's date moves to 2026-10-09, and the curated summary says how the Wayback import changed. Nothing is reworded. Co-Authored-By: Claude Fable 5.1 <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
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.
What and why
The
v0.3.0tag cannot point at the #339 merge (6242e01) any more:pnpm audit --prodthere reports the sevennextadvisories that #389 and #390 patched, anddocker-publish.ymlruns that audit, so the release's Docker job would fail. The tag has to point at current main instead.That leaves the six PRs merged after the prepare (#385, #387, #388, #389, #390, #391) shipping in 0.3.0 while their changelog entries sit under Unreleased. This PR moves them where they belong, so the tagged commit's
CHANGELOG.mddescribes what the build contains:## [0.3.0]. Nothing is reworded. Unreleased is empty again.## [0.3.0]heading's date moves to 2026-10-09. If you tag on a later day, change it again.Only
CHANGELOG.mdchanges.package.json,src-tauri/Cargo.tomlandCargo.lockare already at 0.3.0 on main.After this merges
Tag this PR's merge commit (not
6242e01) with a signed, annotatedv0.3.0from your own identity and push it; the release workflow starts from the tag push. Themacos-signingenvironment still needs a required reviewer before the preflight will pass.How it was verified
pnpm test:release: 30 passed, 0 failed.node scripts/check-release.mjsreads version 0.3.0, tagv0.3.0, minimum macOS 13.5.releaseNotes()on the result: 6,551 characters, no em dashes; Unreleased has no body; each moved bullet is followed by exactly one blank line and the next heading.pnpm audit --prodagainst this branch's lockfile: no known vulnerabilities (against6242e01's: 7).🤖 Generated with Claude Code