Skip to content

The tools-ref defaults follow the tag too - #49

Merged
bdbarnett merged 1 commit into
mainfrom
ci/tools-ref-follows-the-tag
Sep 22, 2026
Merged

bdbarnett merged 1 commit into
mainfrom
ci/tools-ref-follows-the-tag

Conversation

@bdbarnett

Copy link
Copy Markdown
Contributor

Found by the pydevices 0.5.0 verification: three reusables carry publishing-tools-ref input defaults still at publishing-v6, and the v11 coordinator does not override them, so a v11 run checks scripts/ out at v6 — the same 'a tag does not contain the tools it runs' class, one level down. Harmless today (the scripts are identical between v6 and v11, the shipped wheels prove it). This sets the defaults to v11, makes cut_publishing_tag.sh rewrite them with the sibling refs, and widens the sibling-refs check to every ref literal in reusable-*.yml. No new tag is cut for it; v12, when something real changes, will be the first tag cut with full coverage.

reusable-build-pydevices-distributions, reusable-synchronize-mip-package and
reusable-validate-pyscript-filesystem-toml check this repository's scripts/
out at a publishing-tools-ref whose default was still publishing-v6, so the
v11 coordinator ran v6's build tools (identical today; found by the 0.5.0
verification). cut_publishing_tag.sh now rewrites those defaults with the
sibling refs, and the sibling-refs check covers every ref literal in the
reusables.
@bdbarnett
bdbarnett merged commit 7db4242 into main Sep 22, 2026
6 checks passed
@bdbarnett
bdbarnett deleted the ci/tools-ref-follows-the-tag branch September 22, 2026 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant