Skip to content

docs: CLAUDE.md — no GitHub Releases (§3.10) #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
StuartMeeks merged 1 commit into from
Oct 6, 2026
Merged

docs: CLAUDE.md — no GitHub Releases (§3.10) #23

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,9 @@ from the tag glob and steps carrying an `EXCEPTIONS.md` entry. This repo has no
so the only permitted difference is `tags: [ 'v*' ]` and the header comment. `audit-drift.sh`
checks this. Change the template first, then every repo — never this file alone.

GitHub releases here are cut by hand, as in every other repo in the estate. A fifth
`release` job used to build them from `CHANGELOG.md`; it was removed as the estate's only
divergence from the canonical workflow. Adding it back needs an `EXCEPTIONS.md` entry.
No GitHub Releases are cut here, or anywhere in the estate: `STANDARD.md` §3.10 makes
nuget.org the only distribution channel. A release is a version bump plus a `v*` tag push,
which triggers the tag-gated `publish` job. Tags stay; Release objects layered on them do
not. A fifth `release` job used to build Releases from `CHANGELOG.md`. It was removed
because it diverged from the canonical workflow, and §3.10 now forbids it outright, so no
`EXCEPTIONS.md` entry can bring it back.
Loading