Skip to content

chore(v8): calculated snapshot versions for canary releases#74

Open
AakashHotchandani wants to merge 1 commit into
v8from
chore/v8-changeset-snapshot-calculated-version
Open

chore(v8): calculated snapshot versions for canary releases#74
AakashHotchandani wants to merge 1 commit into
v8from
chore/v8-changeset-snapshot-calculated-version

Conversation

@AakashHotchandani

Copy link
Copy Markdown
Collaborator

What

Adds "snapshot": { "useCalculatedVersion": true } to v8's .changeset/config.json — mirroring main, which already has it.

"ignore": [],
"snapshot": {
  "useCalculatedVersion": true
}

Why

release.yml's Canary step (workflow_dispatch, canary=true) runs:

npx changeset version --snapshot canary
npx changeset publish --no-git-tag --tag canary

Without this config, changeset version --snapshot emits 0.0.0-canary-<datetime>. With it, it emits <next>-canary-<datetime> — e.g. 8.49.0-canary-20260722… — matching how v9/main canaries look on the canary dist-tag.

Scope / safety

Version-config only. The snapshot block is read exclusively by changeset version --snapshot. It has no effect on the normal changeset version path that drives the official release (the "Version Packages" PR → 8.49.0) or on changeset publish. So this can merge before or after the Version PR with no interaction.

Recommended order for a clean pre-release: merge this → run Canary (while changesets are still pending) → merge the Version PR → run Publish.

Add snapshot.useCalculatedVersion:true to .changeset/config.json (mirrors main).
release.yml's canary step runs 'changeset version --snapshot canary'; without this
it emits 0.0.0-canary-<datetime> instead of <next>-canary-<datetime>
(e.g. 8.49.0-canary-...). Version-config only — does NOT affect the normal
'changeset version' (official release) path.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@AakashHotchandani
AakashHotchandani requested a review from a team as a code owner July 22, 2026 13:37
@AakashHotchandani
AakashHotchandani requested review from anish353 and dandonarahul2002 and removed request for a team July 22, 2026 13:37
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