Skip to content

release: fold the entries merged after the 0.3.0 prepare into 0.3.0 - #392

Merged
AdamXweb merged 1 commit into
mainfrom
release/v0.3.0-fold
Oct 9, 2026
Merged

AdamXweb merged 1 commit into
mainfrom
release/v0.3.0-fold

Conversation

@adamXbot

@adamXbot adamXbot commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

What and why

The v0.3.0 tag cannot point at the #339 merge (6242e01) any more: pnpm audit --prod there reports the seven next advisories that #389 and #390 patched, and docker-publish.yml runs 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.md describes what the build contains:

  • The eight entries under Unreleased (1 Added, 2 Changed, 2 Fixed, 3 Security) move to the end of the matching subsection of ## [0.3.0]. Nothing is reworded. Unreleased is empty again.
  • The ## [0.3.0] heading's date moves to 2026-10-09. If you tag on a later day, change it again.
  • The curated summary's "Label history back to 2021" bullet gains three sentences on feat(wayback): import archive history at archive.org's pace, finding changes instead of sweeping quarters #391, since the Wayback import now behaves differently in a way users will notice. The draft release body is that summary: 6,551 characters (GitHub's limit is 125,000), no other change to it.

Only CHANGELOG.md changes. package.json, src-tauri/Cargo.toml and Cargo.lock are already at 0.3.0 on main.

After this merges

Tag this PR's merge commit (not 6242e01) with a signed, annotated v0.3.0 from your own identity and push it; the release workflow starts from the tag push. The macos-signing environment 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.mjs reads version 0.3.0, tag v0.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 --prod against this branch's lockfile: no known vulnerabilities (against 6242e01's: 7).

🤖 Generated with Claude Code

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>
@adamXbot
adamXbot requested a review from AdamXweb as a code owner October 8, 2026 13:52
@AdamXweb
AdamXweb merged commit 940a8c6 into main Oct 9, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants