kevinveenbirkenbachandClaude Opus 5 94d607fd0a feat(update): let a version pin declare its own upstream source ...

The Docker updater watches image plus version, the repository updater
repository plus ref. Twelve pins fell outside both - an app_version, a
release, a tag in a registry neither speaks - so nothing ever told anyone
they had gone stale.

Such a pin now names its upstream next to itself in an `update:` block:
git_tags, registry_tags, npm, http_regex or a role-local script, with
`match` selecting a tag flavour and `strip` removing a prefix the pin does
not carry. utils/update/source.py resolves them beside the two existing
updaters, `python -m cli.contributing.update.source` bumps them, the
update-version-sources job opens one PR per role, and
tests/external/update/source warns while a bump is pending.

Two lints hold the rule: every semver pin is watched by one of the three
updaters or opted out with a reason, and a semver only ever sits behind
`version`, `<what>_version` or `ref` - which renames moodle's release to
app_version and simpleicons' local_version to local_tag, the latter being
the tag of a locally built image rather than an upstream version. A
declaration naming a key the entity does not carry, or a type the resolver
does not know, fails the lint instead of resolving nothing in silence.

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

2026-09-22 21:11:58 +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

…

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

…

test_repository.py

…

test_source.py

feat(update): let a version pin declare its own upstream source

2026-09-22 21:11:58 +02:00