chore: Remove the one-shot CLI release version override now that 3.0.0-beta.31 shipped

[hatayama]

Summary

• Removes the temporary "release-as": "3.0.0-beta.31" from the cli package in release-please-config.json, as planned in chore: Unblock the v3-beta release: align the next CLI release with the stamped version and stop release PRs failing the CLI version check #1325.

User Impact

• None at runtime. Without this cleanup, every future CLI release would be pinned to 3.0.0-beta.31; the next CLI release now computes normally from the manifest (3.0.0-beta.32 and onward).

Verification

• scripts/test-release-please-config.sh: green

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1d893f0d-5d1c-4af5-b60c-ead3182e6e92

📥 Commits

Reviewing files that changed from the base of the PR and between 7f30d7e and a049099.

📒 Files selected for processing (1)

• release-please-config.json

💤 Files with no reviewable changes (1)

• release-please-config.json

---

📝 Walkthrough

Walkthrough

The release-as override that pinned the CLI package to version 3.0.0-beta.31 is removed from release-please-config.json, enabling the CLI package to use automatic versioning based on its configured release-type and other settings instead of a hardcoded release tag.

Changes

CLI Release Configuration

Layer / File(s)	Summary
Remove CLI release-as override release-please-config.json	The "release-as": "3.0.0-beta.31" field is removed from the packages.cli configuration, allowing the CLI package to be versioned automatically according to its release-type setting.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• hatayama/unity-cli-loop#1104: Removing the release-as override for packages.cli in release-please-config.json is directly related to the release sync changes because the new sync script/workflows derive per-package release tags from release-please-config.json (including tag composition flags), so the CLI package tag format will change.
• hatayama/unity-cli-loop#1017: The main PR's removal of the release-as pin in release-please-config.json is part of the same v3 beta release automation setup that the retrieved PR updates in the Release-Please/npm publish workflows.
• hatayama/unity-cli-loop#1089: Both PRs modify release-please-config.json's packages.cli release settings (main removes the release-as override, retrieved retargets the CLI release to the repo root and updates related release-please manifest/scripts), so they're directly connected at the release-configuration level.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and specifically describes the main change: removing a temporary release version override for the CLI package now that version 3.0.0-beta.31 has shipped.
Description check	✅ Passed	The description is directly related to the changeset, explaining why the temporary release override is being removed and its impact on future releases.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/remove-cli-release-as-override

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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