chore: bump version to 2.3.15

[zackees]

Cuts release 2.3.15. Rolls up the fixes shipped since 2.3.14:

• Stale standalone-zccache references in CI / Docker / docs / tests (post-embedded-zccache transition) #855 (chore: remove stale standalone-zccache references (#855) #883) — drop stale standalone-zccache CI/Docker/docs references after the soldr embedded-zccache transition (soldr#977/#980/#1081)
• fbuild-daemon: status_manager.rs:221 block_in_place panics in current-thread runtime tests #865 (fix(daemon): write daemon status via sync write_atomic (#865) #884) — write daemon status via sync write_atomic; unblocks fbuild-daemon unit tests on macOS/Windows by eliminating the block_in_place panic in current-thread tokio runtimes
• ESP32 compile on Windows: 'Cannot create temporary file in C:\Windows\' — uncovered tempfile callsite #875 (fix(compile): pin TMP/TEMP for compiler subprocess on Windows (#875) #885) — pin TMP/TEMP for compiler subprocess on Windows; ESP32 compile no longer fails with Cannot create temporary file in C:\Windows\ on the very first TU
• policy: dump_usb_ids must remain (tier-1 source for online-data aggregation) #720 (docs: record dump_usb_ids anti-removal policy (#720) #886) — record anti-removal policy for dump_usb_ids example
• Editable source install does not stage fbuild._native #829 (fix(install): stage fbuild._native during source/editable install (#829) #887) — stage fbuild._native cdylib during source/editable install so from fbuild import ... works after uv pip install -e .

Plus all prior #664 platform_packages audit work, the #826 testing followups, and the build cancellation fix (#853) from earlier in the cycle.

Per docs/RELEASING.md — the Autonomous Release workflow tags + builds + uploads to PyPI once this lands on main.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 41 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9985fd55-822b-4779-9875-908f055d24d7

📥 Commits

Reviewing files that changed from the base of the PR and between 2f52510 and 7a7e26a.

📒 Files selected for processing (2)

• Cargo.toml
• pyproject.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-2.3.15

---

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