From 6f3fbcd7bf9865137a2e5a3f957bbf489e3205d7 Mon Sep 17 00:00:00 2001
From: Cassondra Roberts <1840295+castastrophe@users.noreply.github.com>
Date: Sat, 7 Nov 2026 02:44:26 +0000
Subject: [PATCH] chore: hold the Changesets CLI below 3 in the Renovate
 baseline

Action v1 reads New tag lines that CLI 3 no longer prints, so releases lose their tags & GitHub releases. Document the pairing in the release standards.
---
 docs/repository-standards.md | 7 ++++++-
 renovate.json                | 5 +++++
 2 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/docs/repository-standards.md b/docs/repository-standards.md
index 9b15725..4d73b59 100644
--- a/docs/repository-standards.md
+++ b/docs/repository-standards.md
@@ -18,7 +18,7 @@ note allows.
 | `.husky/post-commit`     | `.husky/post-commit`         | Runs `opx` hooks & lint; never blocks a commit. A repository with its own hooks (`pre-commit`, `commit-msg`) keeps them |
 | `.env.example`           | `.env.example`               | Lists every variable the repo reads; required only where it reads some |
 | `.github/CODEOWNERS`     | `.github/CODEOWNERS`         | One line, `* @castastrophe`; the ruleset requires code owner review |
-| `.github/renovate.json`  | `renovate.json`              | One-month release age, monthly lockfile refresh  |
+| `.github/renovate.json`  | `renovate.json`              | One-month release age, monthly lockfile refresh, & `@changesets/cli` held below 3 |
 | `.github/release.yml`    | `release.yml`                | Changelog categories keyed on `type:` labels     |
 | `.gitignore`             | `.gitignore`                 | Add `_site` for repos that build an Eleventy site, & `coverage` for every repo with tests |
 
@@ -173,6 +173,11 @@ a `GITHUB_TOKEN` wherever `yarn run version` runs. The starter config uses the d
 generator instead; [opx#41](https://github.com/allonsy-studio/opx/issues/41) tracks an
 opt-in for the custom format.
 
+Changesets CLI 3 & `changesets/action@v1` do not work together: the action reads `New tag:`
+lines that CLI 3 no longer prints, so a release gets no git tag or GitHub release. The baseline
+Renovate config holds `@changesets/cli` below 3. Move the CLI & the action to v2 together, in
+one pull request, then drop the rule in that repository.
+
 `opx release` is in beta (`0.1.0-beta.2` at the last check). Plain Changesets commands work
 on the same files where it is not adopted yet.
 
diff --git a/renovate.json b/renovate.json
index 1005166..0513777 100644
--- a/renovate.json
+++ b/renovate.json
@@ -11,6 +11,11 @@
 		{
 			"matchDatasources": ["npm"],
 			"minimumReleaseAge": "1 month"
+		},
+		{
+			"description": "Hold the Changesets CLI at 2 while the release workflow uses changesets/action@v1, which reads CLI 2 output. Move both to 3 together, with changesets/action@v2.",
+			"matchPackageNames": ["@changesets/cli"],
+			"allowedVersions": "<3"
 		}
 	],
 	"rebaseWhen": "behind-base-branch",