AndrewDryga Cut a release
Read the release runbook in full and execute that
canonical runbook in order. Cross-read the current changelog entries and use
/content-director for both the plain-text website summary and the Markdown
GitHub release notes.
Do not duplicate or improvise the release procedure here. The invariants are:
- product tag, changelog entry,
portal/VERSION, and anchor describe one window; LICENSE.mdcarries that release's three-year BUSL Change Date;- tags are signed and verified before push;
- the complete portal gate is green before the release commit;
- every
git push, tag push, andgh release createrequires explicit user confirmation because it leaves the machine.
After publication, verify the signed tag, GitHub release, changelog page/feed, and any release workflow triggered by the tag. The owning Coop task and git history are the completion record.