chore(ci): converge ci-workflows pins on 0.1.24 - #56
Merged
Merged
Conversation
Previous pins in this repository: ci.yml 1ab6708b,9231ee74; security.yml 1ab6708b,9231ee74. A fleet audit found eight distinct ci-workflows pins in use across the estate, from 0.1.11 (88 commits behind main) to 0.1.21. 0.1.24 is the convergence target rather than 0.1.23 because 0.1.23 could not be one. Vendoring left five `uses:` pointing at `./actions/...`, which in a called workflow resolves against the caller's workspace instead of ci-workflows, so every cross-repository caller failed at job setup. ci-feedback.yml had carried that defect since 0.1.21 and only surfaced on 2026-09-20 because its job fires solely on a failed conclusion. 0.1.24 names and pins the repository for all five. Input contracts were diffed across every reusable this repository calls for the whole 0.1.16..0.1.24 range: no input was removed and none became required, so this is a pin move with no caller change. Signed-off-by: rldyourmnd <danil@nddev.it.com> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Converges this repository's
NDDev-OpenNetwork/ci-workflowspins on the published 0.1.24 tag (37a827f921f62353664fc4bcd872f05b65efe71a).Why 0.1.24 and not 0.1.23
An estate-wide audit found the fleet spread across eight distinct
ci-workflowspins, from 0.1.11 (2026-08-26, 88 commits behindmain) to 0.1.21, several of them untagged development commits. 0.1.23 was cut as the convergence target and then could not be one:vendoring had left five
uses:pointing at./actions/.... In a called workflow that resolves against the caller's workspace, never againstci-workflows, so every cross-repository caller failed at job setup.ci-feedback.ymlcarried the defect from 0.1.21. Its job fires only on a failed conclusion, so three releases shipped with the CI-feedback path silently unable to publish anything. Confirmed bygithub-device-syncrun 35541640707.private-security-bundle-free.ymlgained four./actions/tool-cachereferences in 0.1.22/0.1.23. Confirmed bysetup-systemsrun 35541466805.0.1.24 names and pins the repository for all five (PR #122). It is the first release where converging is actually correct.
Safety
Input contracts were diffed for every reusable this repository calls across the whole
0.1.16..0.1.24range: no input was removed and none became required. This is a pin move with no caller change.The retired GARM label classes (
nddev-linux-standard,nddev-linux-untrusted,nddev-linux-integration) were checked against every workflow in all 68 active repositories: zero occurrences. Live runners advertise exactlyself-hosted,Linux,X64,nddev-linux— 24 of them, 6 organization-scope and 18 repository-scope, all online.Every pin uses the
# 0.1.24release-comment form thatcheck_pinned_actions.pyrequires.🤖 Generated with Claude Code