Skip to content

build(deps): bump step-security/harden-runner from 2.20.1 to 2.21.0 - #4718

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/step-security/harden-runner-2.21.0
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/step-security/harden-runner-2.21.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 20, 2026 •

Copy link
Copy Markdown
Contributor

Bumps step-security/harden-runner from 2.20.1 to 2.21.0.

Release notes

Sourced from step-security/harden-runner's releases.

v2.21.0

What's Changed

  • Support for denied endpoints in block mode. This is included in the enterprise tier. Customers can deny outbound calls, for example, to public package registries.
  • Improved Support for AWS CodeBuild GitHub Actions Runners.
  • Bug fixes.

Full Changelog: step-security/harden-runner@v2.20.1...v2.21.0

Commits
  • 05e3151 Merge pull request #684 from step-security/rc-42
  • 0f37afa fix: ignore denied-endpoints on non-enterprise tier
  • 93b58ee fix: resolve cache host read-first and never downgrade egress policy
  • e7399dd fix: align deny-list mode detection with agent and log when both endpoint inp...
  • c16689f test: add denied_endpoints to Configuration fixtures and cover deny-list merge
  • 40b99cf Merge pull request #682 from rohan-stepsecurity/rp/feat/codebuild-self-v2
  • fedec02 Merge branch 'rc-42' into rp/feat/codebuild-self-v2
  • 5361fb1 feat: add build artifacts
  • 286474f feat: Support Bravo agent install on CodeBuild runners
  • 051ec05 Merge pull request #683 from h0x0er/jatin/deny-list
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Aug 20, 2026
@dependabot
dependabot Bot requested a review from a team August 20, 2026 15:18
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Aug 20, 2026
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Aug 20, 2026
Bumps [step-security/harden-runner](https://github.com/step-security/harden-runner) from 2.20.1 to 2.21.0.
- [Release notes](https://github.com/step-security/harden-runner/releases)
- [Commits](step-security/harden-runner@b09bb98...05e3151)

---
updated-dependencies:
- dependency-name: step-security/harden-runner
  dependency-version: 2.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(deps): bump step-security/harden-runner from 2.20.0 to 2.21.0 build(deps): bump step-security/harden-runner from 2.20.1 to 2.21.0 Aug 21, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/step-security/harden-runner-2.21.0 branch from 9d815ea to 8668763 Compare August 21, 2026 02:06
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Aug 21, 2026
@bolichen97
bolichen97 enabled auto-merge (squash) August 24, 2026 06:58
iamwhatever pushed a commit that referenced this pull request Aug 25, 2026
The self-heal sweep rescues a `pending` verdict on age and a `failure` verdict on
later check evidence. Two freeze modes fell outside both tests and had no other
recovery path, because the sweep is the only thing that recomputes an unchanged
commit once its `workflow_run` events are spent.

An UNPUBLISHED verdict was the live one. `pr-readiness.yml` deliberately does not
retry its status POST -- a retry can overwrite a concurrent run's newer verdict --
and instead instructs a human to re-run the workflow. When that POST fails the SHA
carries no readiness status at all, so there is no `pending` to age out, and the
sweep skipped the PR on the assumption that its own run was still coming. The one
case the publisher delegates to a re-run was the one case nothing re-ran. PR #2783
proves it: both readiness runs for f014465 failed on `gh: HTTP 503` from the POST
on 2026-08-17, and eight days later the PR was still MERGEABLE with no readiness
verdict of any kind. Today's #5282 hit the same POST with a 502 and survived only
because an unrelated later event happened to republish. Rescued now on the PR's
own last-activity age, which a push bumps, so the grace window restarts on every
new revision and a genuinely queueing run is left alone.

A STALE GREEN was the unsafe-direction gap. The re-run mechanism behind mode 2 is
direction-blind: a job re-run that flips a lane red after a green verdict emits no
`workflow_run: completed` either, leaving the required aggregate green over a
now-red revision -- which PERMITS a merge, where a stale red only blocks one. The
`*)` arm skipped it as "success needs no rescue". `success` and `error` now share
mode 2's evidence test, narrowed to failure-class conclusions: housekeeping
check-runs (`Strip stale workflow-change override`, `Fork workflow-change guard`)
legitimately complete days after a verdict, so an unnarrowed "any check completed
later" test would re-fire most green PRs every sweep while proving nothing. No
live poisoned green was found in the current 250 open PRs -- the one candidate,
#4272, turned out to be exactly that housekeeping false positive -- so this arm
closes the mechanism, not an observed incident.

`--paginate` WITHOUT `--slurp` was a latent defect in the pre-existing `failure`
arm, found in review and fixed in both arms. gh concatenates one JSON document per
page and jq evaluates each separately, so `max` emits one timestamp PER PAGE;
`date -d` then rejects the multi-line string, the epoch reads 0, and the PR is
skipped. That silently exempted every PR with more than 100 check-runs, which on
this repo is any PR whose lanes have been re-run -- #4718 alone carries ~90.
Verified against the live API: three pages produced three `max` lines unslurped
and one slurped.

The statuses read is now checked for FAILURE before its filter runs. A 503 and a
genuinely absent status both yield empty jq output, and the new unpublished arm
dispatches on the latter -- so without this, transient GitHub trouble would re-fire
arbitrary old PRs every 15 minutes, on a shared token budget, which is the same
exhaustion that causes the missing verdict in the first place.

`--limit 300` on the open-PR listing is raised to 900 with a loud warning when the
ceiling is hit, here and in the two sibling sweeps that share the defect
(fork-pr-label.yml, pr-merge-conflict-label.yml, both found in review). `gh pr
list` returns newest-first and truncates silently, so a ceiling near the real count
drops the OLDEST PRs -- precisely the frozen or unlabelled ones each sweep exists
to catch. At 250 open the old value was already at 83% of its ceiling. Same
truncation class as the `pr_status_report` limit bug. `gh label list --limit` in
those files counts labels, not PRs, and is untouched.

The unpublished case is carried as a sentinel `state` rather than an early record
write, so it reuses the single staleness comparison and the single stale-file
record writer instead of restating either. GitHub's status states are
error/failure/pending/success, so the sentinel cannot collide.

Not addressed here, because the fix is a policy decision rather than a defect: a
required lane that did not exist when the head SHA was pushed can never be
satisfied, and a recompute re-derives `not started` forever. #3089 and #3037 are
frozen on First Principles Review, which became blocking in #4253 but only exists
from #3436. Auto-skipping the lane would let an unreviewed PR pass, so it wants a
rebase or a deliberate eligibility rule. Filed as #5957.

Test plan:
- test/test_pr_readiness_sweep.py: 31 passed (18 pre-existing, 13 added).
  - unpublished: rescued past the window, left alone inside it, respects
    MAX_DISPATCH, fails closed on an unparseable timestamp, still reads as
    unpublished when only a foreign-context status exists, and is NOT triggered by
    a failed statuses read.
  - stale green: rescued for all six failure-class conclusions, never rescued by
    a later pass, self-terminating on republish, untouched with no evidence.
  - pagination: evidence on a SECOND page is found by both arms, which is what
    an unslurped `--paginate` cannot do.
  - truncation: the ceiling is a variable, and a hit is reported.
  - the context-isolation test now proves a foreign status cannot DRIVE the
    decision, rather than relying on the absent-status shape it used to assert.
  - the gh stub models `--paginate --slurp` (outer array of pages) and can fail a
    statuses read on demand, so both fixes are exercised rather than assumed.
- Revert-verify: undoing each of the seven properties independently (unpublished
  arm, green arm, ceiling, failure-class narrowing, slurp on each arm, statuses
  transport guard) fails a named test; tree restored to 31 green.
- test_workflows_conformance / test_workflow_permissions / test_github_workflow_security
  / test_pr_quality_gates / test_ai_review_workflows + the sweep suite: 289 passed.
- check_black_formatting.py and flake8 clean; all three workflows parse as YAML.
- test_pr_readiness_publish.py has 4 pre-existing failures on this host (local jq
  rejects `label` as an identifier); identical on pristine main, untouched here.
bolichen97 pushed a commit that referenced this pull request Aug 26, 2026
…#5955)

The self-heal sweep rescues a `pending` verdict on age and a `failure` verdict on
later check evidence. Two freeze modes fell outside both tests and had no other
recovery path, because the sweep is the only thing that recomputes an unchanged
commit once its `workflow_run` events are spent.

An UNPUBLISHED verdict was the live one. `pr-readiness.yml` deliberately does not
retry its status POST -- a retry can overwrite a concurrent run's newer verdict --
and instead instructs a human to re-run the workflow. When that POST fails the SHA
carries no readiness status at all, so there is no `pending` to age out, and the
sweep skipped the PR on the assumption that its own run was still coming. The one
case the publisher delegates to a re-run was the one case nothing re-ran. PR #2783
proves it: both readiness runs for f014465 failed on `gh: HTTP 503` from the POST
on 2026-08-17, and eight days later the PR was still MERGEABLE with no readiness
verdict of any kind. Today's #5282 hit the same POST with a 502 and survived only
because an unrelated later event happened to republish. Rescued now on the PR's
own last-activity age, which a push bumps, so the grace window restarts on every
new revision and a genuinely queueing run is left alone.

A STALE GREEN was the unsafe-direction gap. The re-run mechanism behind mode 2 is
direction-blind: a job re-run that flips a lane red after a green verdict emits no
`workflow_run: completed` either, leaving the required aggregate green over a
now-red revision -- which PERMITS a merge, where a stale red only blocks one. The
`*)` arm skipped it as "success needs no rescue". `success` and `error` now share
mode 2's evidence test, narrowed to failure-class conclusions: housekeeping
check-runs (`Strip stale workflow-change override`, `Fork workflow-change guard`)
legitimately complete days after a verdict, so an unnarrowed "any check completed
later" test would re-fire most green PRs every sweep while proving nothing. No
live poisoned green was found in the current 250 open PRs -- the one candidate,
#4272, turned out to be exactly that housekeeping false positive -- so this arm
closes the mechanism, not an observed incident.

`--paginate` WITHOUT `--slurp` was a latent defect in the pre-existing `failure`
arm, found in review and fixed in both arms. gh concatenates one JSON document per
page and jq evaluates each separately, so `max` emits one timestamp PER PAGE;
`date -d` then rejects the multi-line string, the epoch reads 0, and the PR is
skipped. That silently exempted every PR with more than 100 check-runs, which on
this repo is any PR whose lanes have been re-run -- #4718 alone carries ~90.
Verified against the live API: three pages produced three `max` lines unslurped
and one slurped.

The statuses read is now checked for FAILURE before its filter runs. A 503 and a
genuinely absent status both yield empty jq output, and the new unpublished arm
dispatches on the latter -- so without this, transient GitHub trouble would re-fire
arbitrary old PRs every 15 minutes, on a shared token budget, which is the same
exhaustion that causes the missing verdict in the first place.

`--limit 300` on the open-PR listing is raised to 900 with a loud warning when the
ceiling is hit, here and in the two sibling sweeps that share the defect
(fork-pr-label.yml, pr-merge-conflict-label.yml, both found in review). `gh pr
list` returns newest-first and truncates silently, so a ceiling near the real count
drops the OLDEST PRs -- precisely the frozen or unlabelled ones each sweep exists
to catch. At 250 open the old value was already at 83% of its ceiling. Same
truncation class as the `pr_status_report` limit bug. `gh label list --limit` in
those files counts labels, not PRs, and is untouched.

The unpublished case is carried as a sentinel `state` rather than an early record
write, so it reuses the single staleness comparison and the single stale-file
record writer instead of restating either. GitHub's status states are
error/failure/pending/success, so the sentinel cannot collide.

Not addressed here, because the fix is a policy decision rather than a defect: a
required lane that did not exist when the head SHA was pushed can never be
satisfied, and a recompute re-derives `not started` forever. #3089 and #3037 are
frozen on First Principles Review, which became blocking in #4253 but only exists
from #3436. Auto-skipping the lane would let an unreviewed PR pass, so it wants a
rebase or a deliberate eligibility rule. Filed as #5957.

Test plan:
- test/test_pr_readiness_sweep.py: 31 passed (18 pre-existing, 13 added).
  - unpublished: rescued past the window, left alone inside it, respects
    MAX_DISPATCH, fails closed on an unparseable timestamp, still reads as
    unpublished when only a foreign-context status exists, and is NOT triggered by
    a failed statuses read.
  - stale green: rescued for all six failure-class conclusions, never rescued by
    a later pass, self-terminating on republish, untouched with no evidence.
  - pagination: evidence on a SECOND page is found by both arms, which is what
    an unslurped `--paginate` cannot do.
  - truncation: the ceiling is a variable, and a hit is reported.
  - the context-isolation test now proves a foreign status cannot DRIVE the
    decision, rather than relying on the absent-status shape it used to assert.
  - the gh stub models `--paginate --slurp` (outer array of pages) and can fail a
    statuses read on demand, so both fixes are exercised rather than assumed.
- Revert-verify: undoing each of the seven properties independently (unpublished
  arm, green arm, ceiling, failure-class narrowing, slurp on each arm, statuses
  transport guard) fails a named test; tree restored to 31 green.
- test_workflows_conformance / test_workflow_permissions / test_github_workflow_security
  / test_pr_quality_gates / test_ai_review_workflows + the sweep suite: 289 passed.
- check_black_formatting.py and flake8 clean; all three workflows parse as YAML.
- test_pr_readiness_publish.py has 4 pre-existing failures on this host (local jq
  rejects `label` as an identifier); identical on pristine main, untouched here.

Co-authored-by: Joe Guo <zejiangg@amazon.com>
@iamwhatever iamwhatever added the needs-pr-triage PR scanner: awaiting automated triage label Aug 26, 2026
@NicholasRBowers NicholasRBowers added needs-author-decision PR blocked on author input and removed needs-pr-triage PR scanner: awaiting automated triage labels Aug 26, 2026
@NicholasRBowers

Copy link
Copy Markdown
Contributor

🤖 Kiro Crew [operator: NicholasRBowers#a942f9ca]: This PR has been inactive for 7+ days. I reviewed the blockers but they require your input:

  • All CI checks pass and the PR is mergeable with no conflicts — there is nothing for automation to fix.
  • The diff bumps the SHA-pinned step-security/harden-runner action from 2.20.1 to 2.21.0 across the five fork-review hardening workflows (egress allowlist). Workflow-security changes need a maintainer's approval to merge (same disposition as the earlier action-bump triage on chore(deps): bump anthropics/claude-code-action from 1.0.194 to 1.0.200 #3324).
  • The inline workflow comments require the new SHA be verified before merge: verified — 05e31511f85b41b11d1cf0ef85d0992719546e2c is exactly the commit the v2.21.0 tag resolves to in step-security/harden-runner.
  • The PR Readiness aggregate was still recomputing after the latest check re-run; no failing check underlies it.

When you've addressed these, the pipeline will re-assess on its next cycle.

@bolichen97

Copy link
Copy Markdown
Contributor

Open PR relationship audit

This is a consolidated, point-in-time code-level audit note. It compares complete merge-base diffs and current/merged code; it does not treat a shared topic as duplication or partial coverage as completion.

DUPLICATE: closing this PR

Close 4718 in favor of the newer PR #8179. Current main still pins harden-runner v2.20.1 in all five fork-review workflows - set by merged PR #3321, whose merge commit 62f21ba is exactly this PR's merge base - so nothing merged has covered the bump and 4718 is not superseded by shipped code. It is superseded by an open PR: PR #8179 performs the identical five-line edit from the same 2.20.1 baseline to the strictly newer 2.21.1, so landing 4718 buys one intermediate release and forces a rebase plus a second maintainer review of a security-sensitive workflow surface. The two cannot both apply. 4718 is still cleanly rebaseable (its anchor line is byte-identical on current main, only shifted by three lines), so REBASE is technically available but pointless while 8179 exists. Operational note: auto-merge (squash) is enabled on 4718 by bolichen97, so that must be disabled before closing, or the PR can merge on its own.

  • DUPLICATE with PR #8179 (OPEN). PR #8179 (opened 2026-09-03, 14 days after this PR) is the newer Dependabot bump of the same action from the same 2.20.1 baseline to the strictly newer 2.21.1, touching the same five lines. Merging 4718 would only force 8179 to rebase and re-review the same security-sensitive surface twice. complete_coverage is false only because 8179 is still OPEN rather than in main - the redundancy is against a competing open PR, not against shipped code. Files: .github/workflows/fork-design-review.yml, .github/workflows/fork-first-principles-review.yml.

The audit recommendation is to close this PR; the relationship target above is the implementation to retain or the merged implementation that already covers it.

No PR, Issue, label, branch, or review state was changed by the relationship-note portion of this audit.

@bolichen97 bolichen97 closed this Sep 4, 2026
auto-merge was automatically disabled September 4, 2026 06:46

Pull request was closed

@dependabot @github

dependabot Bot commented on behalf of github Sep 4, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/github_actions/step-security/harden-runner-2.21.0 branch September 4, 2026 06:46
@github-actions github-actions Bot removed the readiness: checking Automated validation is still running label Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code needs-author-decision PR blocked on author input

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants