chore: automate npm publishing - #58
Merged
Merged
Conversation
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.
Automates npm releases from verified Git tags using trusted publishing and provenance. Pull requests run a publication-free package dry run, while tagged releases require the protected
releaseenvironment before the verified tarball can be published.The package validator checks every public entry point, native sources, bundled agent skill metadata, unresolved workspace ranges, and repository-only files. The TypeScript build is also scoped to
srcso documentation declarations are no longer included in the npm package.Validation:
yarn format:checkyarn lintyarn test --runInBand(84 tests)yarn buildnpm packplusscripts/check-package.mjs