From ef697844ee216b2df08711e0ee4227ca7e527553 Mon Sep 17 00:00:00 2001 From: Taylan Pince Date: Tue, 20 Oct 2026 15:46:07 +0200 Subject: [PATCH 1/2] ci(release): bump every v2 package together via fixed versioning `linked` only aligns versions among packages that are already being bumped, so the 2.3.48 release left core and other untouched packages at 2.3.47. `update-version` reads core's version, so VERSION (sent by the provider as clientVersion) would have stayed at 2.3.47 while the provider shipped as 2.3.48. Switch to `fixed` and include the unscoped `0xsequence` package so any changeset releases every package at one version, as PUBLISHING.md describes. Co-Authored-By: Claude Opus 5.5 --- .changeset/config.json | 3 ++- .changeset/fixed-v2-versions.md | 4 ++++ PUBLISHING.md | 3 ++- 3 files changed, 8 insertions(+), 2 deletions(-) create mode 100644 .changeset/fixed-v2-versions.md diff --git a/.changeset/config.json b/.changeset/config.json index fdcd0b973..277f57074 100644 --- a/.changeset/config.json +++ b/.changeset/config.json @@ -7,7 +7,8 @@ } ], "commit": false, - "linked": [["@0xsequence/*"]], + "fixed": [["@0xsequence/*", "0xsequence"]], + "linked": [], "access": "public", "baseBranch": "v2", "ignore": [], diff --git a/.changeset/fixed-v2-versions.md b/.changeset/fixed-v2-versions.md new file mode 100644 index 000000000..dc0867e43 --- /dev/null +++ b/.changeset/fixed-v2-versions.md @@ -0,0 +1,4 @@ +--- +--- + +Release all v2 packages at one fixed version so the embedded VERSION matches the release diff --git a/PUBLISHING.md b/PUBLISHING.md index 452a642a8..b80547847 100644 --- a/PUBLISHING.md +++ b/PUBLISHING.md @@ -14,7 +14,8 @@ approval steps, failure recovery, and one-time setup. The differences on this br - **Release gates:** build (which includes typecheck), lint, and the release script tests, run before the release bot token is minted. The per-package test matrix in `tests.yml` already runs on every push to `v2`, including the release PR merge. -- **Linked versions:** all `@0xsequence/*` packages are `linked`, so a release stages every package at one version. +- **Fixed versions:** all `@0xsequence/*` packages and `0xsequence` are `fixed`, so any changeset bumps every + package and a release stages them all at one version (the one `update-version` embeds from `@0xsequence/core`). ## Day-to-day: add a changeset From 70e066e05befb4f65a4b7ccb4fade551b1e164a8 Mon Sep 17 00:00:00 2001 From: Taylan Pince Date: Wed, 21 Oct 2026 09:11:17 +0200 Subject: [PATCH 2/2] fix(release): use a core patch changeset to realign v2 versions The empty changeset bumps nothing, so fixed versioning had no bump to spread and the next release would stage the remaining 2.3.48 packages with core and VERSION still at 2.3.47. A patch changeset for core makes Changesets bump the whole fixed group to 2.3.49. Clarify in PUBLISHING.md that only non-empty changesets bump the group. Co-Authored-By: Claude Opus 5.5 --- .changeset/fixed-v2-versions.md | 1 + PUBLISHING.md | 8 +++++--- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/.changeset/fixed-v2-versions.md b/.changeset/fixed-v2-versions.md index dc0867e43..af169ffea 100644 --- a/.changeset/fixed-v2-versions.md +++ b/.changeset/fixed-v2-versions.md @@ -1,4 +1,5 @@ --- +'@0xsequence/core': patch --- Release all v2 packages at one fixed version so the embedded VERSION matches the release diff --git a/PUBLISHING.md b/PUBLISHING.md index b80547847..2eafab2f3 100644 --- a/PUBLISHING.md +++ b/PUBLISHING.md @@ -14,8 +14,9 @@ approval steps, failure recovery, and one-time setup. The differences on this br - **Release gates:** build (which includes typecheck), lint, and the release script tests, run before the release bot token is minted. The per-package test matrix in `tests.yml` already runs on every push to `v2`, including the release PR merge. -- **Fixed versions:** all `@0xsequence/*` packages and `0xsequence` are `fixed`, so any changeset bumps every - package and a release stages them all at one version (the one `update-version` embeds from `@0xsequence/core`). +- **Fixed versions:** all `@0xsequence/*` packages and `0xsequence` are `fixed`, so any non-empty changeset bumps + every package and a release stages them all at one version (the one `update-version` embeds from + `@0xsequence/core`). Empty changesets bump nothing, so they cannot realign versions on their own. ## Day-to-day: add a changeset @@ -24,4 +25,5 @@ pnpm changeset ``` The `Changeset check` CI job fails a PR into `v2` that touches a package without one -(`pnpm changeset add --empty` for changes with no consumer impact). +(`pnpm changeset add --empty` for changes with no consumer impact; an empty changeset satisfies the check but +releases no packages).