Skip to content

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

Open
dependabot[bot] wants to merge 3 commits into
fix/account-unification-lock-20260819from
dependabot/github_actions/step-security/harden-runner-2.21.0
Open

build(deps): bump step-security/harden-runner from 2.20.1 to 2.21.0#105
dependabot[bot] wants to merge 3 commits into
fix/account-unification-lock-20260819from
dependabot/github_actions/step-security/harden-runner-2.21.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 19, 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 compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Open in Devin Review

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 added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Aug 19, 2026

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

  • Problem: Failed same-head checks remain for 72de5499d6e97ae7f7bd804ab78b3e1644dd5a4f.
  • Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
  • Fix: Read and fix the failed check logs below, then rerun the current-head checks.
  • Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow: hourly-product-development.yml"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow: hourly-product-development.yml"]
  R1 --> V1["actionlint plus required checks"]
Loading

@opencode-agent

opencode-agent Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 72de5499d6e97ae7f7bd804ab78b3e1644dd5a4f
  • Workflow run: 32311495420
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

  • Problem: Failed same-head checks remain for 72de5499d6e97ae7f7bd804ab78b3e1644dd5a4f.
  • Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
  • Fix: Read and fix the failed check logs below, then rerun the current-head checks.
  • Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow: hourly-product-development.yml"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow: hourly-product-development.yml"]
  R1 --> V1["actionlint plus required checks"]
Loading

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

  • Problem: Failed same-head checks remain for 72de5499d6e97ae7f7bd804ab78b3e1644dd5a4f.
  • Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
  • Fix: Read and fix the failed check logs below, then rerun the current-head checks.
  • Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Workflow: hourly-product-development.yml"]
  S1 --> I1["GitHub Actions review job"]
  I1 --> R1["Review risk: Workflow: hourly-product-development.yml"]
  R1 --> V1["actionlint plus required checks"]
Loading

@seonghobae

Copy link
Copy Markdown
Contributor

Exact-head failure analysis for 72de549: account-unification-tests fails at uv sync --locked because the base pyproject requires coverage 7.15.4 and setuptools 84.0.0 while this head still carries the prior 7.15.2 and 83.0.0 lock entries. Reproduced with uv 0.12.5. PR #112 is the existing lock refresh for this root cause and has terminal-success Checks; keep #105 behind that protected merge, then update this branch and rerun exact-head Checks. No self-approval or predecessor evidence transfer.

Copy link
Copy Markdown
Contributor

Exact-head failure evidence for 72de5499d6e97ae7f7bd804ab78b3e1644dd5a4f: CI run 32248499293, job 96054138352, failed at uv sync --locked --extra dev with The lockfile at uv.lock needs to be updated. Realm and Compose validation passed. This is the lockfile prerequisite covered by #112 (f02acf93367a40dbfb23a73985017dca8d42ff39); after #112's protected merge, re-fetch this exact PR head and rerun all Checks rather than duplicating the lock change here.

Copy link
Copy Markdown
Contributor

Exact-head fix pushed: ef03c5a93c891980588b125f6c774fa84bf0feef.

The exact-head CI failure was the same stale account-unification lockfile at uv sync --locked. Cherry-picked the validated #112 lockfile resynchronization commit while preserving the harden-runner update.

Local verification at this exact tree: locked dependency sync and the complete account-unification pytest suite passed; git diff check passed. Workflow syntax validation also passed (with only the repository's pre-existing informational shellcheck warning outside this change).

@opencode-agent please independently review this exact head and revalidate all terminal Checks. Do not self-approve, merge, or enable auto-merge.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

@seonghobae
seonghobae changed the base branch from main to fix/account-unification-lock-20260819 August 20, 2026 23:41
@seonghobae

Copy link
Copy Markdown
Contributor

Stacked this dependency PR on the lock-refresh base fix/account-unification-lock-20260819 (PR #112) because it changes uv.lock. The exact current head is ef03c5a93c891980588b125f6c774fa84bf0feef; its refreshed-base rollup has 19 successful and 1 queued Check with no terminal failure. Please bind independent review and any approval to this exact head; do not transfer stale approval or self-approve.

@seonghobae

Copy link
Copy Markdown
Contributor

@opencode-agent @cwl-noema-review Please perform a fresh independent review anchored to exact current head ef03c5a. Re-check the current base, complete diff, and terminal/queued Checks; bind any review to this SHA only. Do not treat prior comments or queued Checks as approval, and do not self-approve or merge.

Copy link
Copy Markdown
Contributor

Current-head review request: exact SHA ef03c5a93c891980588b125f6c774fa84bf0feef has no unresolved inline threads, but reviewDecision remains CHANGES_REQUESTED and one Check is pending. Please re-evaluate the current head after the lockfile prerequisite and publish a fresh independent review.

Copy link
Copy Markdown
Contributor

Review only exact current HEAD ef03c5a93c891980588b125f6c774fa84bf0feef against fix/account-unification-lock-20260819@f02acf93367a40dbfb23a73985017dca8d42ff39. Current inline findings are absent; re-evaluate the harden-runner update and inherited lockfile/security contracts. Do not modify or merge.

…github_actions/step-security/harden-runner-2.21.0

Copy link
Copy Markdown
Contributor

Review only exact current HEAD 77f83dfb2c4611345c0d48f92fceaa6195b4630c against base fix/account-unification-lock-20260819@f02acf93367a40dbfb23a73985017dca8d42ff39. The normal branch update now includes the lock-refresh base; re-evaluate the harden-runner update and inherited lockfile/security contracts. Do not modify or merge.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant