[castastrophe]

What

Add a Renovate rule to the baseline that holds @changesets/cli below 3, & document why in the release standards.

Why

changesets/action@v1 reads New tag: lines that Changesets CLI 3 no longer prints, so a release published with that pair gets no git tag or GitHub release. That happened to glob-concat-cli 2.0.0. A Renovate bump to CLI 3 would break any repo on action v1 the same way.

How

One packageRules entry in renovate.json with allowedVersions: "<3", & a paragraph in the Releases section of docs/repository-standards.md. Repositories copy the baseline, so each repo that releases with Changesets needs its own pull request; the Renovate row of the matrix will flag the ones that differ.

Test plan

1. yarn lint passes
2. Renovate stops proposing @changesets/cli 3 in a repo that has the rule

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6f3fbcd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR