kevinveenbirkenbachandClaude Opus 5.5 4c955d080f feat(update): fail a declared update source whose pin is not a semver ...

The version-source resolver orders upstream versions by semver. A pin that
is not one, such as `latest` or a branch name, has no depth, so no candidate
ever matches it and the declaration never moves anything. Nothing reported
that: the watched-pins lint only looks at values that already are a semver.

test_version_keys now fails on an `update:` block whose pinned key does not
hold a semver. A monitored addon the resolver does not read is held to the
same rule as soon as it pins a `version`, because the catalog check skips a
non-semver pin just as silently. An addon without a `version` keeps tracking
the app default and is left alone.

The Stalwart README no longer asks for `webui_version` to be bumped by hand
next to the image tag. Its `update:` block names the upstream tags, the
server itself follows `releases/latest` of the bundle, and the resolver
plans v1.0.5 to v1.0.11 for it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-05 12:48:22 +02:00

..

__init__.py

…

test_addons.py

…

test_base_pin_families.py

feat(update): read a release line written before the number as a family

2026-09-17 17:43:13 +02:00

test_base.py

…

test_collection_source.py

feat(update): retune the preferred collection source from measured latency

2026-09-16 20:59:45 +02:00

test_docker_release_groups.py

test(update): build the release-group fixture from the role-file constant

2026-09-17 19:26:41 +02:00

test_docker.py

…

test_galaxy.py

fix(lint): put the cache-read markers where the rule reads them

2026-09-16 22:00:30 +02:00

test_repository.py

…

test_source.py

feat(update): fail a declared update source whose pin is not a semver

2026-10-05 12:48:22 +02:00