Skip to content

ci: add canary release on push to main#8

Merged
bntvllnt merged 1 commit intomainfrom
ci/canary-release
Mar 27, 2026
Merged

ci: add canary release on push to main#8
bntvllnt merged 1 commit intomainfrom
ci/canary-release

Conversation

@bntvllnt
Copy link
Copy Markdown
Contributor

Summary

  • Adds canary.yml workflow: auto-publishes pre-release to npm on every push to main
  • Version format: {package.version}-canary.{sha7} (e.g., 0.2.0-canary.abc1234)
  • Published under canary npm tag — does not affect latest
  • OIDC provenance for supply chain security
  • Concurrency group cancels stale canary runs

How it works

push to main
  → typecheck + test + build
  → stamp version: 0.2.0-canary.{sha7}
  → npm publish --tag canary --provenance

Consumers install canary: pnpm add @vllnt/convex-mcp@canary
Stable releases remain via publish.yml (triggered by GitHub Release).

Test plan

  • Workflow syntax valid (YAML linted)
  • Verify canary publishes after merge (check npm @vllnt/convex-mcp@canary)

Publishes pre-release to npm on every push to main:
- Version: {package.version}-canary.{sha7} (e.g., 0.2.0-canary.abc1234)
- npm tag: canary (does not affect `latest`)
- OIDC provenance for supply chain security
- Runs typecheck + test + build before publish
- Concurrency group cancels stale canary runs
@bntvllnt bntvllnt merged commit 730f171 into main Mar 27, 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