Repository navigation
ci: surface npm trusted publishing failures - #14
Closed
ScriptedAlchemy wants to merge 1 commit into
Closed
ScriptedAlchemy wants to merge 1 commit into
ScriptedAlchemy wants to merge 1 commit into
Conversation
commit: |
gioboa
approved these changes
Oct 7, 2026
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.
The release job for
0.1.0passes build, test, format, and package checks, then fails with npmE404while uploading@module-federation/vinext@0.1.0-next.37488551350. npm 12 suppresses OIDC exchange failures at its default log level and falls back to the placeholder registry token generated byactions/setup-node.Remove
registry-urlfrom setup-node so a failed OIDC exchange cannot fall back to that placeholder, and enable verbose publish logging so the registry's exchange error is visible. Keep publishing through the existing GitHub Actions workflow with OIDC.Validation:
actionlintpasses for.github/workflows/release.yml;git diff --checkpasses. No local publishing was attempted.This improves the failure behavior; it does not yet resolve the registry-side rejection. Verify the package's trusted publisher is configured for GitHub owner
module-federation, repositoryvinext, workflowrelease.yml, environmentPublish, and permits directnpm publish. The original release remains failed and the attempted version is absent from npm. Package settings require a signed-in npm session to establish the exact mismatch.