releasinglisted
Install: claude install-skill qiaeru/skills-github
# Release procedure
Pick the bump per semantic versioning: patch for bug-fixes only, minor for any new user-visible feature, major for breaking changes that require user or operator action. Read it off the repo rather than from memory of the session: the headings under `[Unreleased]` (only `Fixed` means patch, any `Added` means minor, a `Removed` or a change users must adapt to means major), or without a CHANGELOG the commit types since the last tag (only `fix:` means patch, a `feat:` means minor, a `!` or a `BREAKING CHANGE:` footer means major). A pre-release (`X.Y.Z-rc.N`, `-beta.N`) follows the naming of the repo's existing tags, is published with `--prerelease` (step 4), and leaves `[Unreleased]` unpromoted unless the CHANGELOG already carries pre-release sections. Read today's date from the shell (`date +%F` or `Get-Date -Format yyyy-MM-dd`, since the bare commands print a locale-dependent format), not from memory: a wrong date in a release heading is public and permanent once the tag is pushed.
The CHANGELOG bullets and the Release notes follow the repo's language, per `committing` step 0. The release commit follows `committing` step 1 (straight to `main` by default, a pull request when the repo requires one, and in that case tag only after the merge), and with `gh` authenticated you publish the Release and check the CI runs yourself. The owner's request to release is the approval to tag and publish; do not ask again, only run the checks in step 4.
## 1. Pre-flight: