Skip to content

Merge main into beta for the 26.7.23.1 release#116

Merged
bharvey88 merged 18 commits into
betafrom
beta-sync
Jul 23, 2026
Merged

Merge main into beta for the 26.7.23.1 release#116
bharvey88 merged 18 commits into
betafrom
beta-sync

Conversation

@bharvey88

@bharvey88 bharvey88 commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Version: 26.7.23.1

What does this implement/fix?

Merges main into beta so the release PR #115 applies cleanly. Brings over what main had that beta lacked:

Conflict resolutions: version kept at the newer beta value 26.7.23.1, and the label-check job stays in its standalone workflow instead of duplicated inside ci.yml.

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

TrevorSchirmer and others added 17 commits April 7, 2026 06:27
Release 26.3.2.1 - New sensors, ESPHome modernisation, and bug fixes
Bumps the github-actions group with 1 update: [pozil/auto-assign-issue](https://github.com/pozil/auto-assign-issue).


Updates `pozil/auto-assign-issue` from 2 to 3
- [Release notes](https://github.com/pozil/auto-assign-issue/releases)
- [Commits](pozil/auto-assign-issue@v2...v3)

---
updated-dependencies:
- dependency-name: pozil/auto-assign-issue
  dependency-version: '3'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
…s/github-actions-3fa3f09d17

chore(ci): bump pozil/auto-assign-issue from 2 to 3 in the github-actions group
Bumps the github-actions group with 2 updates: [pozil/auto-assign-issue](https://github.com/pozil/auto-assign-issue) and [actions/checkout](https://github.com/actions/checkout).


Updates `pozil/auto-assign-issue` from 3 to 4
- [Release notes](https://github.com/pozil/auto-assign-issue/releases)
- [Commits](pozil/auto-assign-issue@v3...v4)

Updates `actions/checkout` from 6.0.2 to 6.0.3
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v6.0.2...v6.0.3)

---
updated-dependencies:
- dependency-name: pozil/auto-assign-issue
  dependency-version: '4'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
- dependency-name: actions/checkout
  dependency-version: 6.0.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
The on_boot publish for apollo_firmware_version was only added to
AIR-1.yaml (b5096d4), but the published firmware is built from
AIR-1_Factory.yaml, and AIR-1_BLE.yaml was also missed. Devices
running shipped firmware never publish the text sensor state, so it
shows blank in HA and the web portal even though device info shows
the project version.

Add the same priority-500 on_boot publish to both files and bump the
version so devices are offered the fixed build.

Fixes #93
…sion

Fix Apollo Firmware Version sensor blank on factory/BLE firmware
…s/github-actions-346f710312

chore(ci): bump the github-actions group with 2 updates
Bumps the github-actions group with 1 update: [actions/checkout](https://github.com/actions/checkout).


Updates `actions/checkout` from 6.0.3 to 7.0.0
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v6.0.3...v7.0.0)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
…ns/github-actions-2217aebe03

chore(ci): bump actions/checkout from 6.0.3 to 7.0.0 in the github-actions group
Replaces inline version-pinned actions with thin callers of
ApolloAutomation/Workflows reusable workflows referenced @main. Leaf
repo now contains zero dependabot-bumpable refs; action version pins
are centralized in the Workflows repo. Dependabot schedule relaxed to
monthly as a safety net.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…lows

Consolidate workflows into shared ApolloAutomation/Workflows reusable workflows
Reconcile for the 26.7.23.1 release PR: keep version 26.7.23.1, fold
the factory/BLE firmware version publish fix (#96) into list-form
on_boot, keep the standalone label-check workflow (no duplicate job
in ci.yml).

🤖 Generated with [Claude Code](https://claude.com/claude-code)
The main merge adds the firmware version publish fix (#96) to the
BLE and Factory variants, so the built firmware changes.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
@bharvey88 bharvey88 added the bugfix Bug fix label Jul 23, 2026
@coderabbitai

coderabbitai Bot commented Jul 23, 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: 5 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 Plus

Run ID: 1d0173df-2e09-4428-b4d2-bd9084ee05a7

📥 Commits

Reviewing files that changed from the base of the PR and between aa1fffc and 53784c6.

⛔ Files ignored due to path filters (1)
  • Datasheets/AIR-1_Datasheet.pdf is excluded by !**/*.pdf
📒 Files selected for processing (7)
  • .github/dependabot.yml
  • .github/workflows/autoassign.yml
  • .github/workflows/ci.yml
  • .github/workflows/weekly.yml
  • Integrations/ESPHome/AIR-1_BLE.yaml
  • Integrations/ESPHome/AIR-1_Factory.yaml
  • PULL_REQUEST_TEMPLATE.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch beta-sync

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.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
@bharvey88 bharvey88 changed the title Merge main into beta for the 26.7.23.2 release Merge main into beta for the 26.7.23.1 release Jul 23, 2026
@bharvey88
bharvey88 merged commit e13fcf4 into beta Jul 23, 2026
11 checks passed
@bharvey88
bharvey88 deleted the beta-sync branch July 23, 2026 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Bug fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants