Skip to content

memory: the release runbook names the npm approval step (nxf 6j6v.c7dd) #4

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
cabcookie merged 1 commit into from
Sep 26, 2026
Merged

memory: the release runbook names the npm approval step (nxf 6j6v.c7dd) #4

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
4 changes: 4 additions & 0 deletions NEXUS_MEMORY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1976,6 +1976,10 @@ COPIES the same bytes and signatures to stable — nothing is rebuilt or re-sign
it then opens a FEED PR (branch release-notes/promote-v<v>): main's ruleset allows no direct push.
A workflow-opened PR starts no checks, so CLOSE AND RE-OPEN it, wait for the checks, MERGE it. Only
that merge puts the stable entry on main and refreshes the public changelog (publish-content.yml).
NPM IS STAGED, NOT PUBLISHED (6j6v.c7dd): release.yml's publish-npm runs `npm stage publish`, so each
tag release leaves @nexus-flow/mcp@<v> WAITING on npm. The owner approves it with 2FA (npmjs.com, or
`npm stage list @nexus-flow/mcp` + `npm stage approve <id>`); the job summary says so. Do NOT re-run
publish-npm for a staged-but-unapproved version: it fails, because npm refuses a second copy.

AND IF PROMOTE EVER COMPLAINS "no beta entry for <v> to promote": do NOT flip the GitHub release
first. Add the entry, re-run `version set`, then fire the promotion. That failure is now structurally
Expand Down
Loading