Repository navigation
ci(release): warn when an npm publish falls back to the token - #160
Merged
Merged
Conversation
npmx.dev flags voidflow as a "trust downgrade" after 0.8.1. The scoped package has been trusted-published on every release despite the immutable OIDC subject; only the unscoped mirror's exchange fails, with "404 package not found", so its trusted publisher entry on npmjs.com is the problem, not npm/cli#9969. Correct the comments and add a step that warns when either package's publisher is not npm-oidc-no-reply@github.com. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
15 tasks
Owner
Author
|
Tracked in #172 (trust entry fix, dropping NPM_TOKEN, then staged publish). Rechecked the registry on 2026-10-14: the scoped package was OIDC on every version, the mirror only at 0.8.1. |
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.
npmx.dev shows a "trust downgrade" for
voidflowafter 0.8.1. The token fallback was blamed on npm/cli#9969 (immutable OIDC subjects), but the publish logs say otherwise:@taraxvoid/voidflowhas been trusted-published on every release, 0.13.0 included (_npmUserisGitHub Actions <npm-oidc-no-reply@github.com>), with this repo's immutable subject.voidflowmirror's exchange fails in the same job:POST .../oidc/token/exchange/package/voidflow 404,package not found. npm then falls back toNPM_TOKEN. 0.8.1 was the last unscoped version that exchanged.So the fix is the trusted publisher entry for
voidflowon npmjs.com (repotaraxvoid/voidflow, workflowrelease-please.yml, environmentnpm), not anything in this workflow.This PR:
::warning::when either package's publisher is not the GitHub OIDC identity. It only warns, because the version is already published either way.🤖 Generated with Claude Code