Automated npm publish via GitHub Actions (#30)
Lets the package ship to npm without a local npm install: publish a GitHub Release and CI runs `npm publish` using an NPM_TOKEN repo secret. - .github/workflows/npm-publish.yml: triggers on release published (and manual dispatch), verifies the release tag matches package.json version, then publishes with provenance (id-token: write) to the public registry. One-time setup by the maintainer: create an npm Automation token and add it as the NPM_TOKEN repository secret. Documented in the workflow header. Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
+4
-1
@@ -9,7 +9,10 @@ each new wave of skills bumps the **major** version, extensions and fixes bump
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
_Nothing yet._
|
||||
### Added
|
||||
- **Automated npm publishing** — `.github/workflows/npm-publish.yml` publishes the package
|
||||
to npm (with provenance) when a GitHub Release is published. Requires a one-time
|
||||
`NPM_TOKEN` repo secret; no local npm needed.
|
||||
|
||||
## [17.0.0] — Agents, Commands & the npx CLI — 2026-06-17
|
||||
|
||||
|
||||
Reference in New Issue
Block a user