memory: the release runbook names the npm approval step (nxf 6j6v.c7dd) - #4
Merged
Merged
Conversation
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 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NhwrYjEtdnS3jCneb57X3k
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Projection of one memory update (
release-cut-runbook, vianxm remember). Since PR #2, each tag release leaves@nexus-flow/mcpstaged on npm until the owner approves it with 2FA. The memory agents read before a release now says so, and it warns against re-runningpublish-npmfor a staged version.Only
NEXUS_MEMORY.mdchanges. It is on the changelog gate's no-impact allowlist, so no label is set:changelog-checkshould pass by itself.🤖 Generated with Claude Code
https://claude.ai/code/session_01NhwrYjEtdnS3jCneb57X3k