fix(ci): pin release tag to triggering commit (Plugin Store tag race)

[simons-plugins]

Fixes the Plugin Store rejection reported for v2026.5.0 ('release tagged 2026.5.0 doesn't match Info.plist 2026.6.0').

Root cause: softprops/action-gh-release creates the tag via the Releases API without target_commitish, which defaults to the default branch's HEAD at creation time. Our stacked-PR merge train landed three merges in ~40s, so #29's release run tagged a commit that already contained #30's version bump. The uploaded zip (built from github.sha's checkout) was internally consistent — only the tag pointed at the wrong commit, and Indigo reads Info.plist at the tag.

Fix: target_commitish: ${{ github.sha }} on the release step. Cleanup (already done): deleted the inconsistent v2026.5.0 release + tag; verified v2026.6.1 (Latest) is consistent.

⚠️ This workflow came from the canonical templates — the same race exists in every repo using them; worth propagating.

2026.6.1 → 2026.6.2 (patch, CI-only + version bump for check-version).

🤖 Generated with Claude Code

https://claude.ai/code/session_01EYAGXd4bE9D9Z5kZeSHeo7

[coderabbitai]

Warning

Review limit reached

@simons-plugins, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

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: defaults

Review profile: CHILL

Plan: Pro

Run ID: b9c6aeae-b692-4e09-8c05-fb60bcfca98f

📥 Commits

Reviewing files that changed from the base of the PR and between 47f6f36 and b723eee.

📒 Files selected for processing (3)

• .github/workflows/create-release.yml
• Indigo MCP Lite.indigoPlugin/Contents/Info.plist
• pyproject.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-tag-race

---

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.}