fix(release): put the v1 line back on changesets/action@v1

[unional]

Closes the break behind #43-style failures now showing up in repobuddy/visual-testing.

What broke

main is the v1 line: pnpm-release-changeset.yml and pnpm-release-changeset-oidc.yml pair changesets/action@v1 with consumers on @changesets/cli v2. Renovate auto-merged three bumps onto it anyway — v2, v2.1.0, v2.1.1 — leaving action v2 running against v1 input names. Every release on the line aborts:

Error: The following inputs have been renamed:
- "publish" -> "publish-script"
- "version" -> "version-script"
- "commit" -> "commit-mesage"

The oidc variant still carries a header comment saying it pairs action v1 with CLI v2, which is how obvious the regression is.

What this does

• Both release workflows go back to changesets/action@v1.
• .github/renovate.json disables major updates for changesets/action. That major is the v1/v2 line boundary — it moves by cutting a new line alongside consumers' CLI major, never by a dependency bump. The Mergify head~=^(?!major-) guard does not match Renovate branch names and so never held it back; that defect is still open separately, this just takes the one dependency that cannot survive it out of Renovate's hands.
• README: repobuddy/visual-testing moves to @changesets/cli ^3.0.0 / @v2 (see ci: pin the shared workflows to @v2, and finish the changesets v3 move visual-testing#844).
• Closes the README's own "Known gap": the workflows' setup-playwright refs move from @main to @v1, so a consumer pinned at @v1 no longer picks the composite action off main. The README said to do this once v1.0.0 was cut, and it has been.

After merging

Re-point the moving alias, or none of this reaches consumers:

git checkout main && git pull
git tag -a v1.0.1 -m "v1.0.1" && git push origin v1.0.1
gh release create v1.0.1 --generate-notes
git tag -f v1 v1.0.1 && git push -f origin v1

Not in this PR

v2.x is on changesets/action@v2.0.0 and its internal setup-playwright refs still say @main. Both want the same treatment on that branch (@v2.1.1 and @v2) plus a v2.0.1 release. Nothing is broken there today, so it is a separate change.

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1f1628f

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

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request