mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
kevinveenbirkenbachandClaude Opus 5
23fcad5ddf
Upstreams that ship several channels in parallel put the channel first: LiteLLM publishes 'main-v1.77.7-stable' next to 'main-v1.77.7-nightly', Jitsi ships 'stable-9646'. The grammar only allowed a leading 'v', so both shapes parsed as nothing at all, sat at depth 0 next to 'latest', and the bump job never looked at them. The numeric core now takes an optional leading channel, and the channel folds into the flavor the same way the patch letter already does. Everything that is not the number is family; only the number is order. That is what keeps '-stable' away from '-nightly' and 'stable-9646' away from a bare '9646', which would leave the channel and change what the role deploys. The change is additive. Only a tag starting with letters followed by a dash can match the new group, and every such tag failed the grammar outright before, so no tag that parses today parses differently. The regression case pins the four shapes that already worked, and the new cases pin the two directions that must not happen along with the tags that must stay refused: 'act-latest', 'bookworm-slim', 'main-latest' and 'buildx-stable-1' carry a channel but no version. Two pins in this repository become orderable as a result: the four Jitsi components and the LiteLLM gateway. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>