cut-release

name	cut-release
description	Cut a Rask release. Use when publishing a new version to NuGet/GitHub. Promotes the CHANGELOG [Unreleased] section to a dated version, then tags vX.Y.Z so MinVer derives the version and release.yml runs the unit gate + sharded E2E + packs and pushes the NuGet packages and GitHub release.

cut-release

Versioning is MinVer from git tags (Directory.Build.props → <MinVerTagPrefix>v</…>). There is no version number to bump in a file — the tag is the version.

Order matters: land the CHANGELOG on main via a PR FIRST, then tag the merged commit. main is a protected branch (no direct pushes — git push origin main is rejected by a hook), and a commitlint check enforces Conventional Commits on every commit. So the release changelog must go through a PR with a Conventional title, exactly like any other change. Tagging afterward keeps the tag on a real main commit (don't tag a local commit you couldn't push).

1. Pre-flight

• On main, clean tree, CI green.
• Run the rask-ship gate once more (format → warnings-as-errors → tests).
• Decide the SemVer bump from the [Unreleased] changes (breaking→major, feature→minor, fix→patch). Pre-1.0, a new feature is still a minor bump (e.g. 0.8.0 → 0.9.0).

2. Promote the CHANGELOG on a release branch

In CHANGELOG.md, rename ## [Unreleased] to ## [X.Y.Z] - YYYY-MM-DD (keep its ### Added/Changed/Fixed/... subsections), and add a fresh empty ## [Unreleased] above it. Commit on a branch with a Conventional Commit message (plain Release vX.Y.Z FAILS commitlint):

git checkout -b release/vX.Y.Z
git add CHANGELOG.md && git commit -m "chore(release): vX.Y.Z"
git push -u origin release/vX.Y.Z

3. PR → merge to main

gh pr create --base main --head release/vX.Y.Z --title "chore(release): vX.Y.Z" --body "…"
# wait for the 14 checks to go green, then:
gh pr merge --squash --delete-branch

Squash lands it as chore(release): vX.Y.Z (#NN) on main (matches prior releases).

4. Tag the merged commit + push (triggers release.yml)

git checkout main && git pull --ff-only        # fast-forward to the merged release commit
git tag vX.Y.Z
git push origin vX.Y.Z                          # push ONLY the tag — main is already up to date

release.yml (on push: tags: v*) runs the unit gate, the sharded E2E matrix, then packs the NuGets (Rask.Server, Rask.Wasm, Rask.Wasm.Hosting, Rask.Validation.DataAnnotations, Rask.Validation.FluentValidation, Rask.Bootstrap, Rask.WebPush, Rask.Cli, …), pushes them to nuget.org, and creates the GitHub release. Watch it (run watch on the bare run id, not a job, exits on the run's conclusion):

gh run list --workflow=release.yml -L 1     # grab the run id
gh run watch <run-id> --exit-status

5. Verify

• GitHub release created with the eight .nupkg assets (gh release view vX.Y.Z).
• Packages visible on nuget.org at version X.Y.Z.
• To undo a mistaken tag before publish completes: git push --delete origin vX.Y.Z. Once release.yml has pushed to nuget.org, the version is permanent (nuget rejects a re-push of the same version) — bump to the next patch instead of retrying X.Y.Z.