Repository navigation
ci: Diagnose npm OIDC exchange in release-snapshot - #506
Merged
Merged
Conversation
Snapshot publishes have returned E404 since September while push-triggered releases with the same trusted publisher still succeed. `changeset publish` hides pnpm's "Skipped OIDC" warning, so print npm's exchange response and the ID token's non-secret claims instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NyYayCPaAA2eaLr74FHJHN
|
Contributor
|
❌ No permission to release snapshot |
2 of 3 tasks
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.
Why
E404onPUT https://registry.npmjs.org/@eddeee888%2f…. Examples are run 44716055633 on chore: Bump @graphql-codegen/* and @graphql-tools/* to latest majors #505 and the Sept 22 run on fix: don't stub every field when a mapper type is unresolvable #455. The last snapshot that published was on Sept 1.release.ymltrusted publisher still publish: 0.20.0, 0.6.1 and 0.5.0 on Oct 7. They use the same pnpm 11.7.0 and Node 24.21+, and the samechangeset publishcommand. The trusted publisher settings on npm are valid (repo,release.yml, no environment).issue_commentvspush), which ends up in the OIDC token. pnpm 11 does the OIDC exchange itself and reports a rejection only as aSkipped OIDC: …warning.changeset publishhides that warning and prints just the finalE404.What
Diagnose npm OIDC exchangestep torelease-snapshot, beforeDeploy snapshot. It does the same exchange pnpm does, for@eddeee888/gcg-server-config, and prints:sub,event_name,ref,workflow_ref,job_workflow_ref,environment, …)tokenremoved and maskedcontinue-on-error: trueand publishes nothing.issue_commentworkflows always run from the default branch, so this step only takes effect after merge. Then trigger a snapshot release on a PR (the usual comment command) and read the step's output. Revert the step once the cause is known.Verification
bash -n)tokenstripping locally with a fake tokenResources
fetchTokenAndProvenanceByOidc: an exchange failure becomesglobalWarn("Skipped OIDC: …")Generated by Claude Code