Context
Consuming unreleased changes in other projects currently means waiting for a stable release. A dev-tag canary stream lets downstream projects pull the latest master build immediately:
pnpm add @zappzarapp/browser-utils@dev
Proposal
Extend the publish flow to push a prerelease canary on every push to master, without touching the latest tag:
- Build, then
npm publish --tag dev --provenance (reuse the existing OIDC trusted-publishing setup from release-please.yml).
- Version scheme that never collides with release-please's stable versions, e.g.
0.0.0-dev.<short-sha> (or <next>-dev.<run_number>).
- Skip on release-please's own release commits (the stable publish already runs).
- Leave
dist-tags.latest untouched; only move dist-tags.dev.
Acceptance
Follow-up from the 2.1.0 release discussion.
Context
Consuming unreleased changes in other projects currently means waiting for a stable release. A
dev-tag canary stream lets downstream projects pull the latestmasterbuild immediately:Proposal
Extend the publish flow to push a prerelease canary on every push to
master, without touching thelatesttag:npm publish --tag dev --provenance(reuse the existing OIDC trusted-publishing setup fromrelease-please.yml).0.0.0-dev.<short-sha>(or<next>-dev.<run_number>).dist-tags.latestuntouched; only movedist-tags.dev.Acceptance
pnpm add @zappzarapp/browser-utils@devinstalls the latestmasterbuilddist-tags.latestis never changed by canary runsFollow-up from the 2.1.0 release discussion.