mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-07 03:15:56 +00:00
kevinveenbirkenbachandClaude Opus 5
e4141cb826
collect_entries walked roles/*/meta/services.yml only, so a repository and ref declared in an addon file was invisible to it. That mattered once84a4b04f0made meta/addons the one place a Discourse plugin is pinned: the pins would have left the updater's view entirely. The other updater cannot stand in, utils/update/docker.py reaches version: through iter_role_images and skips any service without an image:.e317f08ac9built the addon contract with its own catalog-driven SPOT in utils/update/addons.py and left repository.py untouched without saying why, so this widens the ref path rather than replacing the catalog one; an addon can be maintained by either. The per-file work moves into _entries_of_file so services.yml and every meta/addons/*.yml share it. Addon entries carry an ("addons", <stem>) prefix on their entity path, which keeps them distinguishable from a service entry holding the same ref. The line index, the semver filter and the per-file "# nocheck: repository-version" suppression apply unchanged. Two tests cover it: an addon ref is collected beside a service ref with its own path and config_path, and a suppressed addon ref yields nothing. Against this repository the extension currently collects nothing, because every addon ref is a branch and is_semver rejects those; the tests are what prove the walk rather than the absence of output. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>