chore: automate npm publishing with trusted provenance - #18
Merged
Merged
Conversation
janicduplessis
approved these changes
Sep 29, 2026
Merged
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.
Automate npm publishing from v* tags through GitHub Actions, following the Hinges release flow. Keep version 0.4.1 unchanged and prepare future version bumps separately.
Reuse existing JavaScript, Android, and iOS CI. Validate the release tag and main ancestry, inspect the package (including formatter exports, web entrypoint, native/codegen/C++ sources), and publish the saved tarball after release-environment approval. Keep artifacts for seven days; verify integrity, provenance, and dist-tags with up to ten minutes for npm processing. Matching versions are skipped without moving newer dist-tags backward.
Disable local npm publication in release-it and correct repository URL casing for provenance. RELEASE.md covers recurring release and recovery steps. No manual dry runs or duplicate Release PR trigger.
Validation: formatting, lint (existing warnings only), 128 Jest tests / two snapshots, nine publishing-safety tests, Bob build, 105-file tarball inspection, actionlint, and diff checks passed. Damaged tarballs with a missing formatter export or wrong repository casing were rejected.
All hosted CI checks passed, including Android and iOS builds. GitHub's release environment is configured with MeliValesca as reviewer and v* tags only. npm trusted publisher is saved and verified: appandflow/react-native-transformer-text-input, release.yml, environment release, with direct npm publish permission. The next intentional release will verify OIDC publication end to end. No version has been tagged or published.