ci: migrate release-please to client-id auth + bump to @v3

[smorin]

Summary

• Bump actions/create-github-app-token from @v2 to @v3 (v2 doesn't accept the modern client-id input).
• Switch auth from RELEASE_PLEASE_APP_ID (deprecated app-id input) to RELEASE_PLEASE_CLIENT_ID (modern client-id input) in both release-please and sync-cargo-lock jobs.
• Add .github/actionlint.yaml to suppress two false positives from actionlint's stale bundled metadata for create-github-app-token@v3 (it doesn't yet know about client-id).
• RELEASE_PLEASE_APP_TOKEN PAT fallback preserved unchanged.

Aligns toggle with the org-wide migration (smorinlabs sibling repos + smorin/doxa-research). After merge + green verification run, the legacy RELEASE_PLEASE_APP_ID secret will be deleted.

Test plan

• CI green on the PR
• After merge, push an empty ci: commit to main and verify the release-please workflow's Mint release-please app token step succeeds with client-id and emits zero deprecation warnings
• Delete RELEASE_PLEASE_APP_ID secret after green verification

[coderabbitai]

Warning

Review limit reached

@smorin, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 49 minutes and 33 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c9cb8c23-58c6-4b66-b238-a33a89962de3

📥 Commits

Reviewing files that changed from the base of the PR and between 399ed65 and 6155ff9.

📒 Files selected for processing (2)

• .github/actionlint.yaml
• .github/workflows/release-please.yml

---

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

[Copilot]

Pull request overview

This PR updates the repository’s release automation workflow authentication to use the modern GitHub App client-id mechanism (required for actions/create-github-app-token@v3), while preserving the existing PAT fallback path, and adds a narrowly-scoped actionlint suppression for known stale bundled metadata.

Changes:

• Bump actions/create-github-app-token usage from @v2 to @v3 in the release automation workflow.
• Migrate GitHub App auth from deprecated app-id/RELEASE_PLEASE_APP_ID to client-id/RELEASE_PLEASE_CLIENT_ID in both jobs.
• Add .github/actionlint.yaml to suppress two specific actionlint false positives for create-github-app-token@v3 + client-id.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.github/workflows/release-please.yml	Switch release-please + Cargo.lock sync jobs to mint tokens via create-github-app-token@v3 using client-id.
.github/actionlint.yaml	Add scoped ignores to silence known actionlint false positives related to client-id on create-github-app-token@v3.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.