chore(pinact): pin/update GitHub Actions

[davidliu]

Automated update by pinact.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4116181

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

[devin-ai-integration]

Note

This report is out of date. Scroll down for Devin Review's latest report on this PR.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[devin-ai-integration]

Devin Review found 1 new potential issue.

1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)

[devin-ai-integration]

🔴 Release workflow fails before publishing

Every release run using changesets/action v2.1.0 rejects the installed Changesets CLI v2.29.8. The legacy version and publish inputs also fail v2 validation.

Learn more

Changesets Action v2 requires Changesets CLI v3 and validates that requirement before selecting release mode. This repository declares @changesets/cli 2.29.8 in package dependencies, so each run exits before creating a version pull request or publishing. After upgrading the CLI, the action still rejects the old workflow input names because v2 renamed them to version-script and publish-script. The token configuration also needs migration to the github-token input if a custom token is intended; setting only GITHUB_TOKEN no longer configures v2.

Example: A push to main starts Release. Dependency installation provides Changesets CLI 2.29.8, then the action reports that CLI v2 is unsupported and publishes nothing.

Recommended fix: Either retain Changesets Action v1, or migrate the repository atomically to Changesets CLI v3. For v2, rename version to version-script and publish to publish-script, and pass any custom token through github-token. Verify that ci:publish preserves CHANGESETS_OUTPUT so the action can detect published packages.

---

Was this helpful? React with 👍 or 👎 to provide feedback.