Configure OSS publishing#1
Open
tembo[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
…ges and Node 24.14.1
This was referenced Apr 9, 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.
Summary
Updated build and publishing configuration to support dual npm registry publishing (GitHub Packages and npm). Changes include:
packageManagertopnpm@10.33.0and corrected repository URLs to point tobeyonkorg24.14.1) and custom mirror configurationcorepackand pnpm, added GitHub Packages publishing alongside npm registryEnables publishing to both
npm.pkg.github.comandregistry.npmjs.orgon version tags.Related Pull Requests