Repository navigation
ESPHome pinned to 2026.10.1, updated by Renovate - #9
Merged
Merged
Conversation
CI installed whatever ESPHome was newest (`pip install esphome`) and docker-compose.yml ran `:stable`, so every build could pick up a release with breaking changes nobody had looked at. requirements.txt now pins one release for CI, docker-compose.yml names the same image tag, and .github/renovate.json5 moves both in one grouped pull request, whose build check compiles the config with the new release. The pull request lists what to check before merging (the changelog's breaking changes, one device flashed first). The weekly scheduled build, which was there to notice a new ESPHome release, is gone: the Renovate pull request does that now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y3rdfcC26D9RnpBBgHWUB3
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ESPHome pinned to 2026.10.1, updated by Renovate
CI installed whatever ESPHome was newest (
pip install esphome) anddocker-compose.yml ran
:stable, so every build could pick up a releasewith breaking changes nobody had looked at. requirements.txt now pins one
release for CI, docker-compose.yml names the same image tag, and
.github/renovate.json5 moves both in one grouped pull request, whose build
check compiles the config with the new release. The pull request lists
what to check before merging (the changelog's breaking changes, one
device flashed first). The weekly scheduled build, which was there to
notice a new ESPHome release, is gone: the Renovate pull request does
that now.
Generated by Claude Code