Add GitHub Actions workflow to auto-publish to npm on release#26
Open
identd113 wants to merge 2 commits into
Open
Add GitHub Actions workflow to auto-publish to npm on release#26identd113 wants to merge 2 commits into
identd113 wants to merge 2 commits into
Conversation
Triggers when a GitHub Release is published. Runs tests first, then publishes to npm using the NPM_TOKEN repository secret. Validates the version isn't already published before attempting. To enable: add an npm Automation token as a repository secret named NPM_TOKEN. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Allows the workflow to be run manually from the Actions tab without needing to create a GitHub Release first. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.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
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
Adds a GitHub Actions workflow that automatically publishes to npm when a GitHub Release is published, or on demand via the Actions tab. Tests run first — publish is blocked if they fail.
One-time setup required
Step 1 — Create an npm Automation token
homebridge-og→ permission: Read and writeStep 2 — Add the token as a GitHub secret
NPM_TOKENThat's it. The workflow will now have publish access.
How to publish a new version
versioninpackage.json, updateCHANGELOG.md, commit and pushv3.2.1)Alternatively, trigger it manually any time from Actions → npm publish → Run workflow.
Test plan
NPM_TOKENsecret added (Steps 1–2 above)🤖 Generated with Claude Code