Prepare and ship a cmux release end-to-end: choose the next version, curate user-facing changelog entries, bump versions, open and monitor a release PR, merge, tag, and verify published artifacts. Use when asked to cut, prepare, publish, or tag a new release.
Run this workflow to prepare and publish a cmux release.
MARKETING_VERSION from GhosttyTabs.xcodeproj/project.pbxproj.git checkout -b release/vX.Y.Zgit describe --tags --abbrev=0git log --oneline <last-tag>..HEAD --no-mergesgh pr view <N> --repo manaflow-ai/cmux --json author --jq '.author.login'. Also check linked issue reporters with gh issue view <N> --json author --jq '.author.login'.@handles.CHANGELOG.md.web/app/docs/changelog/page.tsx renders from CHANGELOG.md.Added, Changed, Fixed, Removed../scripts/bump-version.sh:
./scripts/bump-version.sh (minor)./scripts/bump-version.sh patch|major|X.Y.ZMARKETING_VERSION and CURRENT_PROJECT_VERSION are updated.Bump version to X.Y.Z.git push -u origin release/vX.Y.Z.gh pr create --title "Release vX.Y.Z" --body "..."gh pr checks --watchmain:gh pr merge --squash --delete-branchgit checkout main && git pull --ff-only./scripts/release-pretag-guard.sh./scripts/bump-version.sh, commit the build-number bump, push/merge that change, and retry the tag.git tag vX.Y.Zgit push origin vX.Y.Zgh run watch --repo manaflow-ai/cmuxcmux-macos.dmg.Credit the people who made each release happen:
— thanks @user! for community code contributions. Use — thanks @user for the report! for bug reporters (when different from PR author). No callout for core team (lawrencecchen, austinywang) — core work is the baseline.### Thanks to N contributors! section at the bottom of each release with an alphabetical list of all [@handle](https://github.com/handle) links (including core team).