Fix npm registry server for publish - #72
Merged
Merged
Conversation
CI publish was failing because npmRegistryServer defaulted to registry.yarnpkg.com (a read-only mirror), not registry.npmjs.org.
alisonjlai
marked this pull request as ready for review
August 19, 2026 20:06
rilescode
approved these changes
Aug 19, 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
2 participants
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.
Problem
The
PublishCI job failed when merging #71 (bump to1.3.0):registry.yarnpkg.comis a read-only npm mirror — it doesn't accept publishes. Yarn falls back to it as a default whenevernpmRegistryServerisn't set explicitly.Root cause
.yarnrc.ymlnever setnpmRegistryServer, so Yarn used its built-in default instead of a real publishable registry.Fix
Explicitly set the registry in
.yarnrc.yml:Testing
After this merges,
1.3.0will need to be published manually one time (since CI only re-triggers publish on a version change, and1.3.0is already merged without one). Future version bumps should auto-publish correctly via CI without a manual step.