Repository navigation
fix: publish npm releases through trusted OIDC identity - #88
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 7, 2026
## [2.31.4](v2.31.3...v2.31.4) (2026-10-07) ### Bug Fixes * publish npm releases through trusted OIDC identity ([#88](#88)) ([378795e](378795e))
|
🎉 This PR is included in version 2.31.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
1 participant
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.
Remove the stored NPM_TOKEN prerequisite and NODE_AUTH_TOKEN from the npm publish job so npm can use the GitHub Actions OIDC identity. Preserve the GitHub-hosted runner, Node 24.11.0, id-token: write permission, version guard and provenance. Add a workflow regression check for OIDC permission and absence of stored publish credentials.
Verified through authenticated npm trust list on September 23: package facult already trusts GitHub repository hack-dance/fclt and workflow release.yml, with publish and stage publish permissions. The listing shows no environment restriction. No trust configuration change was necessary.
Validation: focused workflow tests, lint, type checking, build, compiled binary verifier, and package dry run passed. Full suite: 1061 passed, one failed (src/audit/agent.test.ts: Codex cold-start isolation receipt). The same failure reproduces on the unchanged primary checkout. This PR does not claim a successful OIDC release; verify that after merge.
The pre-commit full-suite hook reproduced that baseline failure. After running lint and validation separately, the commit was made with HUSKY=0 to publish this draft for review.