Dual-publish to GitHub Packages alongside npmjs.org - #13
Merged
Conversation
Keeps the whole @SilverAssist scope resolvable from a single registry for consumers whose .npmrc scopes @SilverAssist to GitHub Packages -- needed because @silverassist/nextjs-core is GitHub-Packages-only (private), and mixing registries within one scope otherwise makes npm treat every other package's lockfile-resolved URL as an untrusted "remote" dependency. Also backports the already-published-version idempotency guard this package never had, so a re-run of this workflow doesn't fail trying to republish an already-current version on either registry.
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.
Summary
GITHUB_TOKEN.Why
Same rollout as the rest of the fleet:
@silverassist/nextjs-coreis private, GitHub-Packages-only, and a consumer scoping@silverassistthere needs every package in the scope reachable, or npm'sallow-remotehardening blocks the mismatched ones onnpm ci.Test plan
npm run checkpasses locally via the pre-push gateactionlinton the changed workflow, no errorsworkflow_dispatch) after merge and confirm the package appears on GitHub Packages