ci: restore secure tokenless npm publishing - #400
Conversation
Remove token-based registry setup that breaks Yarn caching with setup-node v7. Scope release permissions, pin actions, and disable persisted credentials so OIDC publishing remains secure. #agentic
PR SummaryLow Risk Overview Also pins workflow actions ( Reviewed by Cursor Bugbot for commit 1779089. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
🟢 Approval recommended
No unresolved review issues were identified.
Pull request overview
Restores secure tokenless npm publishing via OIDC while tightening release workflow security.
Changes:
- Removes token-based registry configuration and dependency caching.
- Scopes write and OIDC permissions to the publish job.
- Pins actions and disables persisted checkout credentials.
- Uses Node 24’s npm and runner-provided GitHub CLI.
File summaries
| File | Summary |
|---|---|
.github/workflows/release-publish.yml |
Implements secure npm publishing and GitHub release creation. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Background
The release workflow began failing during Node setup after setup-node v7 stopped exporting a placeholder NODE_AUTH_TOKEN. Yarn then attempted to expand the missing token from the generated npm configuration before npm could publish through OIDC.
What Has Changed
Screenshots/Video
N/A — no visual changes.
Checklist