Skip to content

Says the release workflow publishes on the tag #186

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
johnnyt merged 1 commit into from
Oct 11, 2026
Merged

Says the release workflow publishes on the tag #186

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
5 changes: 3 additions & 2 deletions .claude/wurk/commit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,8 +47,9 @@ that is a commit-time concern: the recipe runs on a release bead the
operator has named, and it still stops short of tagging, pushing and publishing.
Those follow `CLAUDE.md`'s authority table: once the prep is merged to
`origin/main`, the conductor or the session that owns the release bead tags
that merged commit, and only the publish (`mix hex.publish`, a GitHub
release) is the operator's, in every campaign.
that merged commit, and the release workflow publishes on the tag push
(ADR-0019): an agent or a session never runs `mix hex.publish`, and a
GitHub release stays the operator's, in every campaign.
What it means for an ordinary commit is only this: if a version change turns
up in the diff and you are not on a release bead, that is the finding -
report it and stop, do not commit it.
Expand Down
Loading