From 3ca1bf1292b8f3f30fdb081dfaa7001c7985520a Mon Sep 17 00:00:00 2001 From: Pieter Viljoen Date: Fri, 17 Jul 2026 20:43:01 -0700 Subject: [PATCH] Registry: ESPHome-Config operational rollout + Dependabot ecosystem resolved 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) --- registry/repos.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/registry/repos.json b/registry/repos.json index 5c1c63b2..113136e1 100644 --- a/registry/repos.json +++ b/registry/repos.json @@ -212,7 +212,7 @@ "requiredSecrets": [], "consumerModel": "pull", "releaseTrigger": "dispatch-only", - "driftNotes": ["ESPHome device config YAML consumed by the cataloged ESPHome-NonRoot image at runtime; distinct from that Docker repo.", "Operational rollout pending: an esphome-config validation job feeding the required check, dispatch-only source-release scaffolding (version.json + NBGV get-version + publish-release.yml, tag + source zip), and develop-as-ground-truth adoption. Dependabot currently covers only the devcontainers ecosystem."] + "driftNotes": ["ESPHome device config YAML consumed by the cataloged ESPHome-NonRoot image at runtime; distinct from that Docker repo."] }, { "name": "HomeAssistant-Config",