chore(ci): clear the last three stale pins — actionlint, diff-cover, jq (#378) - #380
Merged
Conversation
actionlint 1.7.7 -> 1.7.12 (+ recomputed checksum) diff-cover 10.3.0 -> 10.5.1 jq 1.7.1 -> 1.8.2 (+ recomputed checksum) One PR rather than three because each is verified by a DIFFERENT CI job — the Lint job runs the new actionlint over these workflows, the Coverage job installs the new diff-cover and runs the suite through the new jq. Green is therefore unambiguous. A red would not be, and would want splitting. Both checksums recomputed from the release artifacts and re-verified against a fresh download, not copied from a release page. actionlint 1.7.12 run locally over every workflow first: clean.
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
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.
Clears the last three stale pins on the currency report (#378).
1.7.71.7.1210.3.010.5.11.7.11.8.2One PR rather than three because each lands in a different CI job, so green here is unambiguous.
A red would not be, and would want splitting — say so rather than debugging a batch.
What was run
Both checksums were recomputed from the release artifacts, not copied from a release page, and
then re-verified against a fresh download of the exact file CI will fetch:
actionlint 1.7.12 run locally over every workflow — the risk with bumping a linter is that the
newer one flags existing files:
jq 1.8.2 answers the filter shape
tests/coverage.shuses (jq-1.8.2,.percent_covered→91.5).What was NOT run
The coverage suite itself — it needs Docker and a kcov container, which is the Coverage job's
whole job. That check is the gate for both diff-cover and jq, and it is the reason those two are in
a PR at all rather than applied blind.
After this
#378 should show every pin current on its next run. The remaining unverified path in this area is
xmrig-bump.yml: it is not blocked the waytool-bump.ymlwas (XMRig lives inrigforge.sh,which GITHUB_TOKEN may push), but it has never actually pushed either, because that pin has been
current every week. Worth proving before the day it matters.