Skip to content

Resolve npm scope-not-found publish failures by using the authenticated user scope#28

Merged
NagyVikt merged 1 commit intomainfrom
agent/codex/20260411-184332-bia-edixai-com-npm-scope-fix-imdeadpool
Apr 11, 2026
Merged

Resolve npm scope-not-found publish failures by using the authenticated user scope#28
NagyVikt merged 1 commit intomainfrom
agent/codex/20260411-184332-bia-edixai-com-npm-scope-fix-imdeadpool

Conversation

@NagyVikt
Copy link
Copy Markdown
Collaborator

Automated by scripts/agent-branch-finish.sh (PR flow).

…ed user scope

Publishing failed with E404 because @recodeecom does not exist in npm for this account context. This change aligns package identity and install docs with the verified npm login scope (imdeadpool) while keeping CLI commands unchanged (gx/guardex).\n\nIt also updates prompt output and tests so publish/update workflows reference the same scoped package and avoid contradictory guidance.

Constraint: Preserve gx/guardex command surface and existing legacy binary aliases\nRejected: Keep @recodeecom scope and require creating org first | blocks immediate publish and adds external setup dependency\nConfidence: high\nScope-risk: narrow\nReversibility: clean\nDirective: If npm account/scope changes again, update package name and all publish/install strings together in one patch\nTested: npm test\nTested: node --check bin/multiagent-safety.js\nTested: npm publish --dry-run --access public\nNot-tested: live npm publish of 5.0.0
@NagyVikt NagyVikt merged commit a281ced into main Apr 11, 2026
7 checks passed
@NagyVikt NagyVikt deleted the agent/codex/20260411-184332-bia-edixai-com-npm-scope-fix-imdeadpool branch April 11, 2026 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant