Registry: ESPHome-Config operational rollout + Dependabot ecosystem resolved - #348
Merged
Merged
Conversation
…esolved The second ESPHome-Config driftNote recorded the operational rollout as pending and Dependabot as devcontainers-only; both are now resolved and verified: the esphome-config validation job feeds the required check, version.json + publish-release.yml ship (2.0.12 released 2026-07-18), develop is the ground truth, and .github/dependabot.yml declares the github-actions ecosystem dual-target on both branches (ESPHome-Config#49, promotion #50). The hub audit (spec/audit.py) now reports the repo clean. Drop the resolved note; keep the first (still-true consumer relationship). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the fleet registry to reflect the current, verified state of ptr727/ESPHome-Config after its operational rollout and Dependabot ecosystem coverage were completed, removing now-stale drift notes.
Changes:
- Removes the stale “operational rollout pending” drift note for
ESPHome-Config. - Removes the stale “Dependabot devcontainers-only” drift note for
ESPHome-Config.
This was referenced Jul 18, 2026
Closed
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.
Reconciles the ESPHome-Config registry entry after its conformance standup (ESPHome-Config#46) and the Dependabot ecosystem fix (ESPHome-Config#49 / promotion #50) completed - same close-out pattern as #329/#335.
The second
driftNoterecorded the operational rollout as pending and Dependabot asdevcontainers-only. Both are resolved and verified from the live repo before dropping the note:version.json+publish-release.ymlpresent; 2.0.12 released 2026-07-18;developis ground truth..github/dependabot.ymldeclaresgithub-actionsdual-target on bothdevelopandmain.python3 spec/audit.py ESPHome-Config(with the Audit gap: no check that Actions-workflow repos track the github-actions Dependabot ecosystem (ESPHome-Config missed it) #346 check now on develop) -> clean; nodependabotDRIFT.The first note (ESPHome device config consumed by the ESPHome-NonRoot image) stays - still true.
spec/validate.pypasses.🤖 Generated with Claude Code