Skip to content

feat: add tag-triggered release workflow#213

Merged
purupurupu merged 1 commit into
mainfrom
feat/release-workflow
Mar 25, 2026
Merged

feat: add tag-triggered release workflow#213
purupurupu merged 1 commit into
mainfrom
feat/release-workflow

Conversation

@purupurupu

Copy link
Copy Markdown
Owner

Summary

  • Add .github/workflows/release.yml triggered on v* tag push
  • Runs full CI checks (fmt, lint, build, test, e2e) before releasing
  • Zips dist/ and attaches to GitHub Release with auto-generated notes
  • Publishes MCP server to npm via NPM_TOKEN secret

Closes #209

Setup required

  • Add NPM_TOKEN to repository secrets (Settings → Secrets → Actions)
    • Create a Granular Access Token on npmjs.com scoped to css-noop-checker-mcp

Release procedure

# 1. Bump version in package.json and mcp-server/package.json
# 2. Commit
git commit -am "chore: bump version to 0.2.0"
# 3. Tag and push
git tag v0.2.0
git push && git push --tags
# 4. Workflow runs automatically

Test plan

  • Merge PR and add NPM_TOKEN secret
  • Tag v0.1.0 on main to test the workflow
  • Verify GitHub Release is created with zip artifact
  • Verify npm package is published

Create GitHub Release with extension zip and publish MCP server to npm
when a v* tag is pushed. Uses npm OIDC trusted publisher for
authentication — no secrets to manage.

Closes #209
@purupurupu
purupurupu force-pushed the feat/release-workflow branch from 7494eb0 to e0b5564 Compare March 25, 2026 11:16
@purupurupu
purupurupu merged commit 9a04fba into main Mar 25, 2026
2 checks passed
@purupurupu
purupurupu deleted the feat/release-workflow branch March 25, 2026 11:19
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.

feat: add release tag workflow with GitHub Release and npm publish

1 participant