Set up npm release publishing with GitHub Actions#38
Merged
Conversation
Publish to npmjs.com from GitHub Releases with lint/build gates, and remove JSR as a described distribution path in user-facing docs. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Publish under the @countertek org namespace so the unscoped name does not need to be claimed. Update install docs and maintainer setup steps. Co-authored-by: Cursor <cursoragent@cursor.com>
Document scoped vs unscoped naming, CI token scopes, Bypass 2FA, and common publish failures. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
ReleaseGitHub Actions workflow that runs on published GitHub Releases, executes lint/build checks, and publishes@countertek/react-native-ble-nfc-readerto npmjs.com with provenance.@countertekpackage.Closes #34
Manual action required
Before the first automated publish can succeed, a maintainer with publish access to the
@counterteknpm organization must:@counterteknpm org — Sign in at npmjs.com, open org settings (or create the org if needed), and ensure your user is an owner or member with permission to publish under@countertek.@countertek/react-native-ble-nfc-readeris published under the org namespace. It does not require the unscoped namereact-native-ble-nfc-readerto be available on npm.@countertekscope or@countertek/react-native-ble-nfc-reader(Access Tokens). Use an Automation token for CI.NPM_TOKENsecret — In this repository:Settings→Secrets and variables→Actions→ create secretNPM_TOKENwith the token value.--access public. The first successful publish creates the package on npm. After merging, cut a GitHub Release to verify the workflow end-to-end.See docs/release.md for the full maintainer checklist.
Test plan
pnpm run lintpasses locallypnpm run buildpasses locallypnpm run testpasses locallyNPM_TOKENand publish a test release on a maintainer machine or via the workflow after merge