build(deps): bump step-security/harden-runner from 2.19.0 to 2.20.0#41
Closed
dependabot[bot] wants to merge 2 commits into
Closed
build(deps): bump step-security/harden-runner from 2.19.0 to 2.20.0#41dependabot[bot] wants to merge 2 commits into
dependabot[bot] wants to merge 2 commits into
Conversation
The quality-gate composite action ran with no caching and compiled cargo-audit from source on every invocation — on PRs via ci-code.yaml and on main via release.yaml's pre-release gate — which is several minutes of wasted work per run, made worse by this repo building dependencies at opt-level 3. Add a shared cargo cache. ci-code.yaml runs only on pull_request, so the cache it needs must live in the default-branch scope (GitHub only lets a branch restore caches created on its base/default branch). A new cache-warm workflow seeds it on push to main, matrix-matched so both x86_64 and aarch64 are covered, and the quality-gate action restores it read-only so both the PR gate and the pre-release gate start warm. Cache keys include runner.arch because both runners report runner.os == Linux. Replace the from-source `cargo install cargo-audit --locked` with taiki-e/install-action, which fetches a prebuilt cargo-audit and verifies it against SHA256 checksums from the action's pinned manifest (plus artifact attestation/signature when the release provides one). The action is pinned by commit hash and the tool by version, so the verified manifest is fixed. Signed-off-by: Steven Noonan <steven@edera.dev>
Bumps [step-security/harden-runner](https://github.com/step-security/harden-runner) from 2.19.0 to 2.20.0. - [Release notes](https://github.com/step-security/harden-runner/releases) - [Commits](step-security/harden-runner@v2.19.0...bf7454d) --- updated-dependencies: - dependency-name: step-security/harden-runner dependency-version: 2.20.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/step-security/harden-runner-2.20.0
branch
from
July 24, 2026 07:28
ed61ecc to
c04af11
Compare
Contributor
Author
|
Looks like step-security/harden-runner is up-to-date now, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/github_actions/step-security/harden-runner-2.20.0
branch
July 24, 2026 07:35
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.
Bumps step-security/harden-runner from 2.19.0 to 2.20.0.
Release notes
Sourced from step-security/harden-runner's releases.
Commits
bf7454dMerge pull request #673 from step-security/fix/aggregate-error-startup-hang1188420Update non-TLS agent to v0.16.2162cfeaUpdate non-TLS agent to v0.16.1eb9e1f4Bring macOS runner updates from PR 6741a10b01Update Windows agent to v1.0.78b4a105Apply npm audit fixes with release-age cooldown3626e03Default TLS status check failures to enabled100e08bUpdate agent-ebpf to v1.8.12774f75fUpdate agent to v1.8.9f312657Extend missing-agent-dir guard to Linux and macOS cleanup paths