Skip to content

chore(deps): update step-security/harden-runner action to v2.22.4 - #80

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/step-security-harden-runner-2.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/step-security-harden-runner-2.x

Conversation

@renovate

@renovate renovate Bot commented May 21, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
step-security/harden-runner action minor v2.19.3 → v2.22.4

Release Notes

step-security/harden-runner

v2.22.4

Compare Source

What's Changed
  • Fixed a Linux agent memory leak that could cause runners to run out of memory during jobs with heavy process or network activity.
  • The workaround for GitHub’s DNS resolver and outbound proxy experiment on GitHub-hosted Linux runners now defaults to enabled when feature flags can’t be fetched.
  • Improved HTTP/2 TLS interception on Linux (enterprise tier).
  • Added retries for failed monitoring API requests, improving reliability of monitoring initialization and raw-event uploads.

Full Changelog: step-security/harden-runner@v2.22.3...v2.22.4

v2.22.3

Compare Source

What's Changed

  • Added support for Avrea-hosted runners (enterprise tier)
  • Fixed unexpected blocking of allowed connections caused by GitHub’s DNS resolver and outbound proxy experiment on GitHub-hosted Linux runners
  • Added a feature flag to disable implicit AWS endpoint allowances on self-hosted Linux runners (enterprise tier)

Full Changelog: step-security/harden-runner@v2.22.2...v2.22.3

v2.22.2

Compare Source

What's Changed

  • Fixed inbound (ingress) network traffic being incorrectly classified as outbound (egress) traffic on macOS
  • Fixed implicit endpoints intended for self-hosted runners being applied to custom VM environments on Linux (enterprise tier)
  • Improved network and DNS tracing, enforcement logic, and process information correlation on Linux (enterprise tier)

Full Changelog: step-security/harden-runner@v2.22.1...v2.22.2

v2.22.1

Compare Source

What's Changed
  • Fixed security rules not initializing on GHES self-hosted runners
  • Fixed GHES connectivity in block mode by implicitly allowing the GHES hostname

Full Changelog: step-security/harden-runner@v2.22.0...v2.22.1

v2.22.0

Compare Source

What's Changed
  • Linux ARM64 support for community tier
  • GHES support for self-hosted VMs (enterprise tier)
  • MacOS and Windows runner deny list support for block policy (enterprise tier).

Full Changelog: step-security/harden-runner@v2.21.1...v2.22.0

v2.21.1

Compare Source

What's Changed

  • Improved performance of the disable-sudo feature.
  • Fixed an issue in the Community tier where new endpoints required by the GitHub Actions runner were not being implicitly allowed in block mode.
  • Fixed the Harden-Runner post step failing on Linux distributions that do not have a merged /usr filesystem layout (for example Debian 11), where /usr/bin/echo does not exist. This mainly affected self-hosted runners.
  • Documentation updates: clarified which features are in the Community (free) vs Enterprise tier.

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

v2.21.0

Compare Source

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

v2.20.1

Compare Source

What's Changed

  • AWS CodeBuild-hosted runner support
  • Implicitly allow single-labeled (internal) domains in block-mode

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

v2.20.0

Compare Source

What's Changed

  • Support for block policy for MacOS and Windows GitHub-hosted runners
  • Support for Bitrise MacOS GitHub Actions runners
  • HTTPS monitoring support for Bun for Linux runners (enterprise tier)

Full Changelog: step-security/harden-runner@v2.19.4...v2.20.0

v2.19.4

Compare Source

What's Changed
  • Improvements for HTTPS Monitoring for the Enterprise tier of Harden Runner

Full Changelog: step-security/harden-runner@v2.19.3...v2.19.4


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from d4f27e9 to 9211fbc Compare June 11, 2026 11:51
@sonarqubecloud

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from 9211fbc to 2eb35d9 Compare July 7, 2026 12:07
@renovate renovate Bot changed the title chore(deps): update step-security/harden-runner action to v2.19.4 chore(deps): update step-security/harden-runner action to v2.20.0 Jul 7, 2026
@renovate renovate Bot changed the title chore(deps): update step-security/harden-runner action to v2.20.0 chore(deps): update step-security/harden-runner action to v2.20.1 Aug 5, 2026
@renovate
renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from 2eb35d9 to 19d489d Compare August 5, 2026 06:10
@renovate
renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from 19d489d to 9f8d348 Compare August 15, 2026 08:50
@renovate renovate Bot changed the title chore(deps): update step-security/harden-runner action to v2.20.1 chore(deps): update step-security/harden-runner action to v2.21.0 Aug 15, 2026
@renovate
renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from 9f8d348 to 12bf86b Compare August 31, 2026 00:41
@renovate renovate Bot changed the title chore(deps): update step-security/harden-runner action to v2.21.0 chore(deps): update step-security/harden-runner action to v2.21.1 Aug 31, 2026
@sonarqubecloud

Copy link
Copy Markdown

@renovate renovate Bot changed the title chore(deps): update step-security/harden-runner action to v2.21.1 chore(deps): update step-security/harden-runner action to v2.22.0 Oct 6, 2026
@renovate
renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from 12bf86b to 0086f04 Compare October 6, 2026 06:03
@renovate renovate Bot changed the title chore(deps): update step-security/harden-runner action to v2.22.0 chore(deps): update step-security/harden-runner action to v2.22.1 Oct 8, 2026
@renovate
renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from 0086f04 to 12b6abb Compare October 8, 2026 02:07
@renovate renovate Bot changed the title chore(deps): update step-security/harden-runner action to v2.22.1 chore(deps): update step-security/harden-runner action to v2.22.2 Oct 20, 2026
@renovate
renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from 12b6abb to e72900a Compare October 20, 2026 11:43
@sonarqubecloud

Copy link
Copy Markdown

@renovate renovate Bot changed the title chore(deps): update step-security/harden-runner action to v2.22.2 chore(deps): update step-security/harden-runner action to v2.22.3 Oct 27, 2026
@renovate
renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from e72900a to 7c5c00c Compare October 27, 2026 22:42
@renovate renovate Bot changed the title chore(deps): update step-security/harden-runner action to v2.22.3 chore(deps): update step-security/harden-runner action to v2.22.4 Nov 6, 2026
@renovate
renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from 7c5c00c to 4cecadd Compare November 6, 2026 19:44
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.

0 participants