Skip to content

ci: Diagnose npm OIDC exchange in release-snapshot - #506

Merged
eddeee888 merged 1 commit into
masterfrom
ci/release-snapshot-verbose-npm-log
Nov 20, 2026
Merged

eddeee888 merged 1 commit into
masterfrom
ci/release-snapshot-verbose-npm-log

Conversation

@eddeee888

@eddeee888 eddeee888 commented Nov 20, 2026 •

Copy link
Copy Markdown
Owner

Why

  • Every snapshot release since Sept 22 has failed with E404 on PUT 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.
  • Push-triggered releases through the same release.yml trusted 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 same changeset publish command. The trusted publisher settings on npm are valid (repo, release.yml, no environment).
  • The remaining difference is the trigger event (issue_comment vs push), which ends up in the OIDC token. pnpm 11 does the OIDC exchange itself and reports a rejection only as a Skipped OIDC: … warning. changeset publish hides that warning and prints just the final E404.

What

  • Adds a Diagnose npm OIDC exchange step to release-snapshot, before Deploy snapshot. It does the same exchange pnpm does, for @eddeee888/gcg-server-config, and prints:
    • the ID token's non-secret claims (sub, event_name, ref, workflow_ref, job_workflow_ref, environment, …)
    • the exchange HTTP status and npm's response body, with any token removed and masked
  • The step has continue-on-error: true and publishes nothing.

issue_comment workflows 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

  • YAML parses and Prettier passes
  • Shell syntax check (bash -n)
  • Checked the token decoding and token stripping locally with a fake token
  • Real run: pending merge, then a snapshot release

Resources


Generated by Claude Code

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
@changeset-bot

changeset-bot Bot commented Nov 20, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 72ce820

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

Copy link
Copy Markdown
Contributor

❌ No permission to release snapshot

@eddeee888
eddeee888 merged commit f856697 into master Nov 20, 2026
19 checks passed
@eddeee888
eddeee888 deleted the ci/release-snapshot-verbose-npm-log branch November 20, 2026 10:26
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.

2 participants