Commit Graph
7 Commits
Author SHA1 Message Date
Willie d824c50780 docs(release): say which pushes to main regenerate the Release PR
The previous wording said every push to main discards edits on the
Release PR. Pushing two docs commits showed otherwise: Release Please
reported the PR "remained the same", since docs commits do not change
the generated notes. Only commits that change the notes rebuild it.
2026-10-04 05:16:28 +08:00
Willie 9bc9a922bc docs(release): sync docs and README before reviewing the Release PR
Doc drift was only found after a release shipped, and the README's
Latest note and contributors were updated by hand when remembered. The
release workflow now starts with a documentation pass over the pending
range, including the README callout and contributors for minor and major
releases, and builds the site the way Website Pages does. It runs before
the changelog review because every push to main regenerates the Release
PR. The site build uses npm, since pnpm 12 in the devcontainer stops on
unapproved build scripts.
2026-10-04 05:15:07 +08:00
Willie 031c33c1b1 ci(test): skip the duplicate push run for release commits (#319)
Merging a Release PR ran the full Test suite twice on the same commit:
once for the push to main, and once from Release Please, which calls
Test with the exact merge SHA before tagging. Skip the push run for
chore(main): release commits; the release gate still runs every job.

The Release PR's own runs stay, because their matrix checks are
required by branch protection, and a skipped matrix job never reports
its per-OS check names, which would block the merge.

A newer push to a pull request now cancels that pull request's running
tests instead of finishing a superseded run.

Validation: actionlint v1.7.12 on all workflows, and a simulation of
every job's condition for push, release gate, pull request, fork pull
request and schedule events against the current workflow.
2026-10-02 03:57:06 +08:00
Willie ba4eedd9f3 ci(release): publish the reviewed release notes instead of the PR body
Release Please fills the draft from its PR body and GoReleaser kept that
body by default, so the draft ignored the reviewed CHANGELOG entry. Replace
it during the draft build.

The published body is the maintainer's specs/RELEASE_NOTES file, applied
to the draft before Publish Release, which keeps it. Document that step and
that Publish Release now also deploys the website.

Validation: goreleaser check (valid; only the known brews deprecation) and
ai-context check.
2026-10-02 02:35:26 +08:00
Willie 4ff5316789 ci(release): deploy the website only from a published release
Pushes to main deployed the website immediately, so docs for unreleased
features went live before the release that ships them. Publish Release now
deploys the released tag after publication, the same way it calls Docker
Publish, and only the Cloudflare secrets are passed to the deploy.

Website Pages can still be dispatched with a tag or branch to redeploy or
ship a docs-only fix.

Validation: actionlint on all workflows and ai-context check.
2026-10-02 02:29:47 +08:00
Willie 1fe668ec54 ci(release): add reviewed version PRs and manual publication
Create Release Please PRs, synchronize release metadata, and test the exact merge commit before tagging and building an unpublished draft.

Verify release artifacts before manual publication and keep Homebrew and Docker distribution tied to the approved version. Document explicit version overrides and squash-merge behavior in the release skills and runbook.

Validation: make check, 12 release helper tests, actionlint, and an isolated six-platform GoReleaser build with artifact verification.
2026-10-02 01:53:47 +08:00
Willie 262e639701 docs: add task-routed agent wiki
Add a shared instruction kernel and byte-budgeted topic router so agents load only task-relevant repository guidance. Wire drift checks into local and CI workflows and point project skills at the routed topics.
2026-09-25 02:32:37 +08:00