Add Firmware Channel switching from HA#79
Conversation
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
bharvey88
force-pushed
the
firmware-channel
branch
from
8998ac1 to
6d094f1
Compare
Same Stable/Beta channel switching as CAST-1 (ApolloAutomation/CAST-1#43 naming): - Firmware Channel select (Stable/Beta) sets the OTA manifest URL via a new apply_ota_source script; each image tracks its own variant's manifests through the ble_firmware substitution. - Firmware Update button force-installs the selected channel's firmware. - build-beta.yml publishes beta builds to a rolling beta pre-release. - build.yml now builds MSR-2.yaml as firmware/ so updates serve the end-user image; the Factory image moves to firmware-factory/ for the web installer only. Beta-channel builds compile thin beta-channel/ wrapper yamls so the Firmware Channel select defaults to Beta on firmware obtained from the beta channel (fresh flashes only; stored choices still win). Version: 26.7.8.1 🤖 Generated with [Claude Code](https://claude.com/claude-code)
bharvey88
force-pushed
the
firmware-channel
branch
from
6d094f1 to
57a98bd
Compare
|
Superseded by #80. MSR-1 shipped the unified redesign as 26.7.9.1 (one image per channel, runtime Bluetooth Proxy switch, no ble_firmware selector / manifest guard), so the two-image channel architecture here is retired before it merged. #80 carries the same beta pipeline plus the http_request buffer fixes this branch predates. |
1 participant
Version: 26.7.7.1
What does this implement/fix?
Same Stable/Beta firmware switching as CAST-1 (naming per ApolloAutomation/CAST-1#43):
apply_ota_sourcescript. Stable = GitHub Pages (main branch builds), Beta = rollingbetapre-release assets. Each image tracks its own variant's manifests through a build-timeble_firmwaresubstitution; there is no user-facing variant switching.betabuild the end-user images and publish them to a rollingbetapre-release, with manifests rewritten to absolute URLs and bins prefixed per variant.MSR-2.yamlasfirmware/and moves the Factory image tofirmware-factory/, which only the web installer uses. On their next update, fielded devices leave the Factory image, drop improv BLE, and reclaim flash.All three variants config-validated on ESPHome 2026.6.4. Not yet tested on hardware.
Types of changes
Checklist / Checklijst:
If user-visible functionality or configuration variables are added/modified:
🤖 Generated with Claude Code