From 491d6a956f6c90968e52a5ea1390c13d86e27c32 Mon Sep 17 00:00:00 2001 From: Tim Benniks Date: Fri, 23 Oct 2026 12:27:01 +0200 Subject: [PATCH] docs: tag and publish a GitHub release as the last release step Co-Authored-By: Claude Opus 5.5 --- docs/contributing/release-and-versioning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contributing/release-and-versioning.md b/docs/contributing/release-and-versioning.md index a365ad4..d05ae49 100644 --- a/docs/contributing/release-and-versioning.md +++ b/docs/contributing/release-and-versioning.md @@ -39,7 +39,7 @@ There are no generated artifacts, so any validated commit on `main` is a coheren 3. Add a section for the new version to [`CHANGELOG.md`](../../CHANGELOG.md), calling out renamed or removed skills. 4. Run `node scripts/validate.mjs`. 5. Confirm CI passes on the pull request. -6. Merge to `main` and tag the release. +6. Merge to `main`, tag `vX.Y.Z` on the merge commit, and publish a GitHub release whose notes are the version's `CHANGELOG.md` section. ## How updates reach users