Release 26.8.19.1: merge beta into main - #112
Conversation
The rolling beta-fw release tag stays on the commit that was default-branch HEAD when the release was first created. gh release create without --target tags default-branch HEAD, and gh release upload never moves the tag, so the published assets track every beta build while the release source commit does not. Add a step to build-beta.yml that PATCHes the beta-fw tag ref to the built commit after each upload, so the tag always matches the assets. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
The Bluetooth Proxy switch does restore from flash, but the _OFF half of RESTORE_DEFAULT_OFF decides the boot where nothing is stored yet, which is the first boot after the switch shipped. MSR-1_BLE.yaml inherited that mode from Core, so legacy BLE devices that had always proxied came up with the proxy off after updating. Core now reads the mode from a bluetooth_proxy_restore_mode substitution defaulting to RESTORE_DEFAULT_OFF, and MSR-1_BLE.yaml overrides it to RESTORE_DEFAULT_ON, the same override pattern the file already uses for its OTA manifest URLs. The unified image is unchanged and a user's saved choice still wins on every later boot. Refs ApolloAutomation/MSR-2#92 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Re-dated for the merge day per versioning policy. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Keep Bluetooth Proxy on for legacy BLE builds
Remove the beta-channel wrapper configs and build the plain variant files on the beta branch, so beta and stable images are identical and the Firmware Channel select always defaults to Stable on a fresh flash. Mirrors CAST-1 #60. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
…ault Update Firmware Select
Re-point beta-fw tag on every beta publish
🤖 Generated with [Claude Code](https://claude.com/claude-code)
|
Warning Review limit reached
Next review available in: 37 minutes Limit details: You’ve used all 2 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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 within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
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 |
Bump Core.yaml version to 26.8.19.1
Resolves the build-beta.yml conflict from #109: keep the beta-channel build paths from #106, take the bumped actions/checkout and esphome/workflows pins from main. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Merge main into beta to align workflow pins
3 participants
Version: 26.8.19.1
What does this implement/fix?
Promotes the beta channel to main. Changes since 26.7.9.1:
Types of changes
Checklist / Checklijst:
If user-visible functionality or configuration variables are added/modified:
🤖 Generated with Claude Code