chore(release): bump fbuild to 2.5.30

[zackees]

Bumps the workspace and Python package to 2.5.30. Merging triggers release-auto.yml, which publishes the GitHub Release and PyPI wheels.

Why now

FastLED's release is blocked on fbuild 2.5.29 regressions fixed on main:

• fix(esp32): resolve unified toolchain by registry version for pioarduino 53.x/54.x #1605: every ESP32 Xtensa env pinned to pioarduino 53.x/54.x failed with toolchain-xtensa-<mcu> not found in platform.json, and 53.x boards failed to link with undefined __dso_handle.
• fix(rp2040): do not infer Bluetooth-only Arduino-Pico libraries when Bluetooth is off #1606: every plain RP2040/RP2350 build (including Blink) selected BTstackLib and failed on its _needsbt.h static_assert.
• ci: remove duplicated cache-key-suffix keys from check-ubuntu.yml #1611: check-ubuntu.yml/ci-minimal.yml were invalid YAML, so no clippy or unit tests ran on main from 10-01. With ci: remove duplicated cache-key-suffix keys from check-ubuntu.yml #1611 merged, linux / Check passed on main's tree.

Release-candidate evidence

The binary built from this branch (fbuild 2.5.30, debug), used via FBUILD_EXECUTABLE with bash compile <board> --examples AutoResearch in FastLED master 85980c9b2f, built successfully on: esp32dev, esp32s3, esp32c6, esp32c3, esp32s2, rp2350, rp2040, rp2350w. With released 2.5.29, esp32dev/s2/s3/c3 and rp2040/rp2350 fail.

The diff only touches version fields: Cargo.toml, pyproject.toml, 21 workspace entries in Cargo.lock, and uv.lock. No third-party dependency moved.

Summary by CodeRabbit

• Chores
  • Updated the release version to 2.5.30. No user-facing feature or behavior changes are included in this release.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: FastLED/fbuild/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 964bf3ca-479a-4a43-ab82-1dfcf48b7a80

📥 Commits

Reviewing files that changed from the base of the PR and between 186b2ee and ca3e390.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (2)

• Cargo.toml
• pyproject.toml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The workspace package version and the Python project version both change from 2.5.29 to 2.5.30.

Changes

Project version update

Layer / File(s)	Summary
Update project versions Cargo.toml, pyproject.toml	Both metadata files change the project version from 2.5.29 to 2.5.30.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to ca3e3

The Rust and Python project versions are aligned at 2.5.30, with no actionable merge risk indicated by the supplied change context.

Architecture Summary

Architecture risk: 🔵 Low · up to ca3e3

The change affects 2 systems.

Changed systems: Cargo.toml, pyproject.toml

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — Cargo.toml (service) was modified; 1 changed file maps to changed impact.
• observed — pyproject.toml (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in Cargo.toml: The workspace package version is updated from 2.5.29 to 2.5.30.
• observed — Modified behavior in pyproject.toml: The project version changed from 2.5.29 to 2.5.30.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: updating fbuild and package versions to 2.5.30 for a release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

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