Skip to content

ci: automated npm publish via GitHub Releases#7

Merged
ccchow merged 2 commits intomainfrom
ci/npm-publish-workflow
Feb 26, 2026
Merged

ci: automated npm publish via GitHub Releases#7
ccchow merged 2 commits intomainfrom
ci/npm-publish-workflow

Conversation

@ccchow
Copy link
Copy Markdown
Owner

@ccchow ccchow commented Feb 26, 2026

Summary

  • Add .github/workflows/publish.yml triggered on GitHub Release publish
  • Clean CI build (checkout → install → build backend → build frontend → verify → publish)
  • Uses --provenance flag for npm supply chain attestation
  • Requires NPM_TOKEN secret configured in repo settings

Setup required after merge

  1. Generate an npm access token at https://www.npmjs.com/settings/~/tokens (type: Automation)
  2. Add it as a repository secret: Settings → Secrets and variables → Actions → New repository secret → name: NPM_TOKEN

Release flow

  1. Bump version in package.json (via PR)
  2. Merge to main
  3. Go to Releases → Draft a new release
  4. Create tag (e.g., v0.2.1), write release notes, click Publish release
  5. Action automatically builds and publishes to npm

🤖 Generated with Claude Code

ccchow and others added 2 commits February 25, 2026 23:30
Triggers on GitHub Release publish. Builds in clean CI environment
with provenance attestation. Requires NPM_TOKEN secret.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
No long-lived token needed. GitHub Actions obtains a short-lived
publish credential via OIDC exchange with npm registry.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ccchow ccchow force-pushed the ci/npm-publish-workflow branch from 0dffcb1 to 3fd6357 Compare February 26, 2026 07:30
@ccchow ccchow merged commit 40938f0 into main Feb 26, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant