Skip to content

Rename Firmware Channel option Main to Stable#43

Merged
bharvey88 merged 1 commit into
ApolloAutomation:betafrom
bharvey88:stable-channel-name
Jul 7, 2026
Merged

Rename Firmware Channel option Main to Stable#43
bharvey88 merged 1 commit into
ApolloAutomation:betafrom
bharvey88:stable-channel-name

Conversation

@bharvey88

Copy link
Copy Markdown
Contributor

Version: 26.7.7.2

What does this implement/fix?

Renames the Firmware Channel select options from Main/Beta to Stable/Beta
(and the initial option to "Stable"). "Stable" is clearer than "Main" for
users who don't know the branch layout, and matches the naming used by the
AIR-1 firmware channel feature (ApolloAutomation/AIR-1#107).

No functional change: the update-source logic keys off "Beta", and devices
that stored "Main" fall back to the initial option, which is the same
channel. Both variants config-validated on ESPHome 2026.6.4.

Types of changes

  • Bugfix (fixed change that fixes an issue)
  • New feature (thanks!)
  • Breaking change (repair/feature that breaks existing functionality)
  • Dependency Update - Does not publish
  • Other - Does not publish
  • Website of github readme file update - Does not publish
  • Github workflows - Does not publish

Checklist / Checklijst:

  • The code change has been tested and works locally
  • The code change has not yet been tested

If user-visible functionality or configuration variables are added/modified:

  • Added/updated documentation for the web page

🤖 Generated with Claude Code

Matches the naming used by the AIR-1 firmware channel feature; "Stable"
is clearer than "Main" for users who don't know the branch layout.
Devices that stored "Main" fall back to the initial option, which is
the same channel.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
@bharvey88 bharvey88 added the new-feature New feature or request label Jul 7, 2026
@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@bharvey88, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 70cd210e-e7e9-4251-addf-3d69df538c1e

📥 Commits

Reviewing files that changed from the base of the PR and between 815df1b and a5ee01e.

📒 Files selected for processing (1)
  • Integrations/ESPHome/Core.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands.

@bharvey88 bharvey88 mentioned this pull request Jul 7, 2026
10 tasks
bharvey88 added a commit to bharvey88/CAST-1 that referenced this pull request Jul 7, 2026
Move label-check out of ci.yml into its own workflow on
pull_request_target so it gets a write token on fork PRs; plain
pull_request tokens are read-only there and the Apply Single Label step
fails (see ApolloAutomation#43). Same fix the other product repos got in June. ci.yml
permissions trimmed to contents: read since the CI build needs nothing
more.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
@bharvey88 bharvey88 merged commit 98d14a8 into ApolloAutomation:beta Jul 7, 2026
7 of 8 checks passed
bharvey88 added a commit to ApolloAutomation/AIR-1 that referenced this pull request Jul 8, 2026
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 AIR-1.yaml as firmware/ so updates serve the
  end-user image; the Factory image moves to firmware-factory/ for the
  web installer only.

Version: 26.7.8.1

🤖 Generated with [Claude Code](https://claude.com/claude-code)
bharvey88 added a commit to ApolloAutomation/MTR-1 that referenced this pull request Jul 8, 2026
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 MTR-1.yaml as firmware/ so updates serve the
  end-user image; the Factory image moves to firmware-factory/ for the
  web installer only.

Version: 26.7.8.1

🤖 Generated with [Claude Code](https://claude.com/claude-code)
bharvey88 added a commit to ApolloAutomation/MSR-2 that referenced this pull request Jul 8, 2026
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.

Version: 26.7.8.1

🤖 Generated with [Claude Code](https://claude.com/claude-code)
bharvey88 added a commit to ApolloAutomation/AIR-1 that referenced this pull request Jul 8, 2026
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 AIR-1.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 added a commit to ApolloAutomation/MTR-1 that referenced this pull request Jul 8, 2026
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 MTR-1.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 added a commit to ApolloAutomation/MSR-2 that referenced this pull request Jul 8, 2026
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant