Add Firmware Channel switching and serve end-user images for OTA#65
Add Firmware Channel switching and serve end-user images for OTA#65bharvey88 wants to merge 1 commit into
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 (21)
✨ 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
3 times, most recently
from
88cbbac to
bc737a1
Compare
Same feature as CAST-1 and AIR-1 (ApolloAutomation/AIR-1#107): - Firmware Channel select (Stable/Beta) sets the OTA manifest URL via a new apply_ota_source script keyed by a per-variant variant_slug substitution ("", "-b", "2", "-b2"), replacing the per-file firmware_update_manifest_url; Firmware Update button force-installs and prevents deep sleep for the download duration. - The four Minimal yamls (the adopted end-user configs) gain the managed update system, and their device identity is aligned with the improv images since they become the images fielded devices update onto. - build.yml now serves the Minimal images at firmware*/; the improv images move to *-factory/ for the web installer only. - build-beta.yml publishes beta builds of all four variants to a rolling beta pre-release. - update component id renamed firmware_update -> update_http_request to match the other Apollo repos, and wifi on_connect refreshes the update entity (same fix as PR #61). The BLE variant yamls also gain the managed update system (they inherit the Firmware Update button and apply_ota_source from Core.yaml, so they must define update_http_request for CI to pass). 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
bc737a1 to
de1f791
Compare
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.firmware/,firmware-b/,firmware2/,firmware-b2/; the improv images move to*-factory/for the web installer only. Per-variant manifests are keyed by avariant_slugsubstitution ("", "-b", "2", "-b2"), replacing the per-filefirmware_update_manifest_url. Minimal image device identity is aligned with the improv images (nothing fielded is renamed;apollo-temp-1b-42kept as-is).wifi: on_connectnow refreshes the update entity - same fix as Fix firmware update entity being stale for 6h after boot #61, so that PR's YAML hunks become redundant (its release-drafter fix stands).betabuild the end-user image(s) and publish them to a rollingbetapre-release with manifests rewritten to absolute URLs.firmware_update->update_http_requestto match the other Apollo repos.All eight configs 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