Repository navigation
build: add npm run release with CI-only publication - #68
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
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.
Add npm run release using np --no-tests --no-publish --branch main, matching the other repositories. np updates the version and pushes the commit/tag; npm publication remains exclusively in GitHub Actions with Trusted Publishing and provenance.
The tag workflow now waits for Compatibility on the exact tagged main commit. Failed/cancelled CI, tags outside main and bounded wait timeout refuse publication. Existing release authorization and publish-time revalidation remain unchanged. Android source publication metadata reads package.json so future version bumps cannot leave Gradle behind. Document the interactive command and npm run release -- patch.
Validation: 28 workflow helper tests and Android release helper tests passed; actionlint, formatting and diff checks passed. The default command rejects non-main branches. An explicit dry-run on the work branch confirms npm version and git push are only planned and no npm publish task exists. No runtime implementation changes.