From d53dd9063a120f6e0bc75f11c03f75146cab785c Mon Sep 17 00:00:00 2001 From: Carsten Koch Date: Sat, 26 Sep 2026 12:29:08 +0200 Subject: [PATCH] memory: the release runbook names the npm approval step (nxf 6j6v.c7dd) The release-cut-runbook memory now says that each tag release leaves @nexus-flow/mcp staged on npm until the owner approves it with 2FA, and that publish-npm must not be re-run for a staged version. Projected into NEXUS_MEMORY.md from the memory store. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01NhwrYjEtdnS3jCneb57X3k --- NEXUS_MEMORY.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/NEXUS_MEMORY.md b/NEXUS_MEMORY.md index f0d7f95..bf6b975 100644 --- a/NEXUS_MEMORY.md +++ b/NEXUS_MEMORY.md @@ -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): 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@ WAITING on npm. The owner approves it with 2FA (npmjs.com, or +`npm stage list @nexus-flow/mcp` + `npm stage approve `); 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 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