ci: attach release job to npm-publish environment#18
Conversation
npm Trusted Publisher config requires the OIDC token to include an environment claim of `npm-publish`; without it, `pnpm changeset publish` fails with E404 on PUT to the registry.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe release workflow now declares an Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
@nebula-agents/electron-mcpis configured with Environment name:npm-publish, but the release job had noenvironment:key. The OIDC token therefore lacked the environment claim andpnpm changeset publishwas rejected with E404 (run 25026312815).environment: npm-publishto thereleasejob so the OIDC claims match what npm expects.npm-publishGitHub Actions environment to exist in repo settings (Settings → Environments). Once created, the next push tomain(or rerun of the failing workflow) should publish 0.1.0.Verification
pnpm checkpnpm test:electronif Electron/CDP behavior changedSummary by CodeRabbit