Repository navigation
Camper@narko: ci(publish): publish through npm trusted publishing, no token - #54
Merged
Merged
Conversation
npm accepts this workflow's GitHub OIDC identity for @agentmuxai/muxcode, so the NPM_TOKEN secret is no longer needed and nothing long-lived is stored. Provenance is attached automatically. npm 11.5.1+ is required, so the job installs npm 11 first. Agent: Camper@narko
There was a problem hiding this comment.
ReAgent Diagnostics
| Field | Value |
|---|---|
| ReAgent Version | 5.34.6+g67922b4 |
| Trigger | PR opened |
| Tier | STANDARD |
| Project Context | No CLAUDE.md |
| Model | claude-sonnet-5-5 |
| Effort | high |
| Ref Repos | Enabled (dev-tools, shared-infrastructure) |
| Merge Safety | No recent-code deletions |
| Review Time | 7s |
| Timestamp | 2026-10-07T00:11:57Z |
| Repository | agentmuxai/muxcode |
| PR | #54 |
LGTM
|
Codex not asked about |
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
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.
Summary
publish.ymlpublished with anNPM_TOKENrepository secret, which was never set, so no version of@agentmuxai/muxcodehas reached npm. AgentMux pins a version of it, so its Mux Code installer fails.This switches publishing to npm trusted publishing. npmjs.com accepts this workflow's GitHub OIDC identity (repo
agentmuxai/muxcode, workflowpublish.yml), so no npm token is created or stored, and provenance is attached automatically.NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}and--provenanceare removed. With trusted publishing there's no token, and provenance is automatic.id-token: writewas already granted.Setup outside this PR
npm can't do the first publish of a brand-new package through trusted publishing; the package must already exist. So, once:
@agentmuxai/muxcode@0.0.0(README andpackage.jsononly) is published by hand by an org owner, to reserve the name.agentmuxai/muxcode,publish.yml.Then pushing the
v0.8.0tag publishes the first real version from CI, and 0.0.0 can be deprecated.Agent: Camper@narko
🤖 Generated with Claude Code