Releasing

Overview

A merge to main that carries a feat:, fix:, security: or breaking commit waits in semantic-release.yml for a reviewer of the release environment. Once a reviewer approves it, the workflow promotes ## [Unreleased] in CHANGELOG.md to the next version.

A maintainer then runs publish.yml by hand with that version. It checks the contract and the tests again, and gh skill publish creates the tag and the release. Both skills release together under that tag.

A pull request whose commits would release needs a typed title, because a squash merge takes its subject from the title.

Installers read the tag. The plugin marketplace reads main, and plugin.json carries no version, so that it always does.

CHANGELOG.md follows Keep a Changelog. A change that alters what a skill does adds a line or two under ## [Unreleased], and the contract fails when one released version has two headings.