Skip to content

chore(ci): clear the last three stale pins — actionlint, diff-cover, jq (#378) - #380

Merged
VijitSingh97 merged 1 commit into
developfrom
chore/bump-ci-pins
Aug 19, 2026
Merged

chore(ci): clear the last three stale pins — actionlint, diff-cover, jq (#378)#380
VijitSingh97 merged 1 commit into
developfrom
chore/bump-ci-pins

Conversation

@VijitSingh97

Copy link
Copy Markdown
Contributor

Clears the last three stale pins on the currency report (#378).

tool from to verified by
actionlint 1.7.7 1.7.12 the Lint job — it runs the new actionlint over these workflows
diff-cover 10.3.0 10.5.1 the Coverage job — it installs and runs it
jq 1.7.1 1.8.2 the Coverage job — the suite runs through it inside the kcov container

One 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_linux_amd64.tar.gz: OK
jq-linux-amd64: OK
  ci.yml carries the actionlint sha: OK
  coverage.sh carries the jq sha: OK

actionlint 1.7.12 run locally over every workflow — the risk with bumping a linter is that the
newer one flags existing files:

actionlint 1.7.12: CLEAN on all workflows

jq 1.8.2 answers the filter shape tests/coverage.sh uses (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 way tool-bump.yml was (XMRig lives in rigforge.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.

  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.
@VijitSingh97
VijitSingh97 merged commit e0d58e2 into develop Aug 19, 2026
9 checks passed
@VijitSingh97
VijitSingh97 deleted the chore/bump-ci-pins branch August 19, 2026 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant