This repository was archived by the owner on Oct 28, 2026. It is now read-only.
Repository navigation
Avoid token-style npm config for OIDC publishing - #315
Merged
Merged
Conversation
Do not ask setup-node to generate npmrc token authentication for the tokenless workflow. Keep dependency and publication registries explicit on their existing commands. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Danny van Velzen (dannyvv)
approved these changes
Oct 28, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Avoid token-style npm config for OIDC publishing
Why
The tokenless setup from #314 fails before dependency installation. setup-node's
registry-urlinput generates an npmrc referencingNODE_AUTH_TOKEN, which isintentionally unset for OIDC; Yarn classic rejects that unresolved reference.
What
so Yarn does not require token authentication configuration.
public-publish registry flags, OIDC permissions, and package version.
Testing
Reproduced the exact Yarn error; tokenless regression, frozen install, build,
both example suites and workflow schema checks passed. Publication was not retried.
Changelog
Should this change be included in the release notes: no. Avoid token-style npm
configuration in the OIDC publishing workflow.
Microsoft Reviewers: Open in CodeFlow