Skip to content

Release 26.8.23.1 - firmware update fix and H-1D publish path - #33

Open
bharvey88 wants to merge 16 commits into
mainfrom
beta
Open

Release 26.8.23.1 - firmware update fix and H-1D publish path#33
bharvey88 wants to merge 16 commits into
mainfrom
beta

Conversation

@bharvey88

@bharvey88 bharvey88 commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Merges beta into main for the 26.8.23.1 release. Changes include:

Merge commit, not squash. Merging triggers Build and Publish on main, which creates release 26.8.23.1 and publishes firmware/ and firmware-d/.

🤖 Generated with Claude Code

TrevorSchirmer and others added 10 commits December 4, 2025 13:58
Fork-submitted PRs get a read-only token on pull_request runs, so the
label and assignee bots fail with 403. pull_request_target runs in the
base repo context with a write token; safe here because neither job
checks out or executes PR code. Build jobs stay on pull_request. Trim
ci.yml permissions to what the builds need.
- The Firmware Update entity pointed at /H-1/artifact/manifest.json,
  which is a 404 (CI publishes to /H-1/firmware/) - the update system
  has never been able to offer an update
- Trigger a manifest check once WiFi connects: the update component's
  first 6h poll fires before the network is up and skips silently,
  leaving the entity stale for ~6h after every boot
- Fix firmare-d -> firmware-d typo in the H-1D publish directory
Home Assistant shows only the first 255 characters of an ESPHome
release summary, so boilerplate is expensive and ## headings render
oversized in the update dialog:

- Render category titles and What's Changed in bold instead of H2
- Drop the star-the-repo footer
- Drop the Full Changelog line: it semver-truncates 4-part versions
  (always links ...X.Y.Z.1) - the shared build workflow now appends
  a correct compare link instead
Fix label-check and auto-assign on fork PRs
Fix firmware update system (404 manifest URL, stale first check)
The README was overwritten with the H-2 one (title, photo link to a
file this repo does not have, 24 LED / four button spec, H-2 charities
and shop link). Rebuilt from the original README (d5137f0) and the
firmware: 22 LEDs, ESP32-C3, three songs on one button. The H-1 shop
page is gone, so the link points at the store root.

Generated with [Claude Code](https://claude.com/claude-code)
# Conflicts:
#	.github/workflows/autoassign.yml
#	.github/workflows/ci.yml
@bharvey88 bharvey88 mentioned this pull request Aug 23, 2026
2 tasks
@coderabbitai

coderabbitai Bot commented Aug 23, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 10cdb48b-e0cd-4325-b5e5-ceba3567b1ce


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 and others added 6 commits August 23, 2026 11:20
Sync main into beta and bump to 26.8.23.1
Fix the H-1 README hardware details
ESPHome 2026.8.0 replaces rgb_order/is_rgbw/is_wrgb with a single
channel_colors key on esp32_rmt_led_strip (esphome#18474).
`channel_colors` only exists from ESPHome 2026.8.0 (esphome#18474), but
these YAMLs still declared an older min_version. Devices adopted through
the ESPHome dashboard track this repo at HEAD with no pinned ref, so on
an older ESPHome the next recompile fails with "Unknown option
channel_colors" pointing into a file the user never wrote, instead of a
clear version error.

ESPHome merges remote packages and checks min_version in the preload
phase, before component schemas load, so the bump produces the right
message. No firmware change: min_version is validation-only and emits no
code, so the compiled binary is unaffected.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Replace deprecated rgb_order with channel_colors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants