ci: publish to npmjs and GitHub Packages#7
Merged
Conversation
…ions The publish workflow now publishes each version to both registries so consumers can resolve @missionsquad/x402-proxy from either. Each publish step checks whether the version already exists on its registry and skips instead of failing, so pushes to main that do not bump the version stay green. Adds packages: write permission and the repository field required for GITHUB_TOKEN publishes to GitHub Packages. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
@missionsquad/missionsquad-corelives on GitHub Packages, so consumer repos scope@missionsquadtonpm.pkg.github.com— which madex402-proxy(npmjs-only) unresolvable there. Registry routing is per-scope, not per-package, so the fix is to publish this package to both registries.0.1.2was already published to GitHub Packages manually; this PR makes CI do it for every future version.Changes
publish.yaml: after the existing npmjs publish, a secondsetup-nodere-points the generated.npmrcatnpm.pkg.github.comand publishes withGITHUB_TOKEN(newpackages: writepermission).npm view <name>@<version>against its registry and skips instead of failing, so pushes tomainthat don't bump the version (like this PR itself) stay green instead of erroring on the duplicate-version publish.package.json: adds therepositoryfield, which GitHub Packages uses to validate/linkGITHUB_TOKENpublishes to this repo.Verification
yarn buildclean with thepackage.jsonchange.@missionsquad/x402-proxy@0.1.2confirmed resolvable from bothregistry.npmjs.organdnpm.pkg.github.com.🤖 Generated with Claude Code