ci: update changesets action to v2 input and output names

[jeffreylouden]

Description

The Release workflow pins changesets/action@198f833 (v2.1.0), but still passed v1 input names, so the step hard-failed:

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

Renamed the inputs, and moved the token from the GITHUB_TOKEN env var to the new github-token input (v2 reads the input and throws if a differing GITHUB_TOKEN env var is also set).

The outputs were renamed too, which the error message does not mention. hasChangesets is now has-changesets. Left as-is, the eight downstream steps guarded on steps.changesets.outputs.hasChangesets == 'false' would have compared an empty string against 'false' and silently skipped — no database build, no checksum, no minisign signature, no GitHub Release. The workflow would have gone green while shipping nothing.

Dashed output names also need index syntax (outputs['has-changesets']) rather than dot access, since - is the subtraction operator in GitHub Actions expressions.

Old	New
version:	version-script:
commit:	commit-message:
title:	pr-title:
env: GITHUB_TOKEN	github-token: input
outputs.hasChangesets	outputs['has-changesets']

Input and output names verified against action.yml at the pinned SHA, not from memory.

Type of Change

• New software/plugin entry
• New hardware entry
• New manufacturer entry
• Update to existing entry
• Bug fix
• Schema or script change

Checklist

• I have run pnpm validate and it passes
• YAML files follow the existing format
• Manufacturer exists (or I'm adding it in this PR)
• Categories and formats are from the schema files
• Identifiers are accurate, if provided (bundle IDs, etc.)

No data/*.yaml files are touched, so the data-oriented checklist items above do not apply. Verified instead: the workflow parses as YAML with the expected with: keys and if: expressions, and prettier --check passes.

Additional Notes

No changeset is included: the Changeset workflow only requires one when data/*.yaml changes, and this is CI-only.

Unaffected but worth noting for later: existential-engineering/racks .github/workflows/release.yml still uses changesets/action@v1 with the old input names. It works today on v1, but a bump to v2 there will hit this same breakage, including the silent output rename (pullRequestNumber → pr-number, which that workflow reads).

---

Generated by Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: d62a7c9

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 41 minutes

Limit details: You’ve used all 2 included reviews currently available under your plan. You completed 81 included PR reviews in the past 7 days; at that activity level, included reviews refill at 2 reviews per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 81cbe323-30b9-416f-b163-a41dc39984bb

📥 Commits

Reviewing files that changed from the base of the PR and between 39b17bc and d62a7c9.

📒 Files selected for processing (1)

• .github/workflows/release.yml

---

_{Comment @coderabbitai help to get the list of available commands.}