chore: bump version to 2.2.10

[zackees]

Summary

Bumps fbuild 2.2.9 → 2.2.10, bundling four user-facing fixes merged on main since 2.2.9.

Fixes shipped in this release

• Build SAMD51J fails: get_core_dir(adafruit) points at nonexistent cores subdir #319 / fix(samd): fall back to cores/arduino when build.core dir is missing #320 — SAMD51: cores/arduino fallback + resolved core_dir injected into include path. Build SAMD51J was 100% red on every main push.
• Build nRF52840 DK fails: variant nRF52DK absent in installed Adafruit framework #321 / fix(nrf52): map PIO nRF52DK variant to Adafruit pca10056 #322 — nRF52: nRF52DK → pca10056 variant alias for the Adafruit framework. Build nRF52840 DK was 100% red.
• fix(boards): catch up tinyuf2 partition rename + whitelist cmsis_dsp_lib (clears 27/39 drift) #318 — Board JSON drift cleanup (tinyuf2 partition rename across 18 Adafruit boards + 4d_systems esp_sr fix + cmsis_dsp_lib validator whitelist). Validate Boards was failing on 39 boards; now ~14 (remaining are configuration-choice differences flagged for maintainer review).
• fix(lint): annotate Python daemon Command::new sites #317 — crates/fbuild-python/src/daemon.rs Command::new annotations after the lib.rs split. Lint subprocess spawns was red — blocked every PR's lint check.

After this lands

Downstream FastLED bumps fbuild==2.2.9 → fbuild==2.2.10 in pyproject.toml to pick up these fixes. That bump will retrigger the workflows that have been stale-red waiting for these fixes:

• Build SAMD51J, Build SAMD21*, Build SAMD51P
• Build nRF52840 DK, nrf52840_supermini
• Validate Boards (down to the configuration-choice remainder)

Release machinery

release-auto.yml triggers on the push to main when Cargo.toml or pyproject.toml changes. No further manual steps needed.

[coderabbitai]

Warning

Review limit reached

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

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

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 52252bfd-03d3-4cbc-9596-9310d095e9f5

📥 Commits

Reviewing files that changed from the base of the PR and between 9eaeddc and 779a246.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 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.2.10

---

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