Skip to content

Releases: step-security/harden-runner

v2.21.1

Choose a tag to compare

@varunsh-coder varunsh-coder released this 30 Aug 23:29
Immutable release. Only release title and notes can be modified.
e14015d

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: v2.21.0...v2.21.1

v2.21.0

Choose a tag to compare

@varunsh-coder varunsh-coder released this 15 Aug 05:52
Immutable release. Only release title and notes can be modified.
05e3151

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: v2.20.1...v2.21.0

v2.20.1

Choose a tag to compare

@varunsh-coder varunsh-coder released this 05 Aug 05:52
Immutable release. Only release title and notes can be modified.
b09bb98

What's Changed

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

Full Changelog: v2.20.0...v2.20.1

v2.20.0

Choose a tag to compare

@varunsh-coder varunsh-coder released this 07 Jul 09:25
Immutable release. Only release title and notes can be modified.
bf7454d

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: v2.19.4...v2.20.0

v2.19.4

Choose a tag to compare

@varunsh-coder varunsh-coder released this 21 May 16:09
Immutable release. Only release title and notes can be modified.
9af89fc

What's Changed

  • Improvements for HTTPS Monitoring for the Enterprise tier of Harden Runner

Full Changelog: v2.19.3...v2.19.4

v2.19.3

Choose a tag to compare

@varunsh-coder varunsh-coder released this 14 May 21:31
Immutable release. Only release title and notes can be modified.
ab7a940

What's Changed

  • Default to audit mode when api-key missing with use-policy-store by @varunsh-coder in #665

Full Changelog: v2.19.2...v2.19.3

v2.19.2

Choose a tag to compare

@varunsh-coder varunsh-coder released this 13 May 20:32
Immutable release. Only release title and notes can be modified.
9ca718d

What's Changed

  • Update the Harden Runner agent for enterprise tier to use go 1.26 and fix minor bugs.

Full Changelog: v2.19.1...v2.19.2

v2.19.1

Choose a tag to compare

@varunsh-coder varunsh-coder released this 02 May 15:27
Immutable release. Only release title and notes can be modified.
a5ad31d

What's Changed

  • fix: detect ubuntu-slim runners early and bail out by @devantler in #657

What the fix changes

  • Harden-Runner will detect ubuntu-slim runners and exit cleanly with an informational log message, instead of post harden runner step failing on chown: invalid user: 'undefined'.

What the fix does not do

  • Jobs running on ubuntu-slim will not be monitored by Harden-Runner. The agent relies on kernel-level features (that require elevated capabilities).
  • Per GitHub's docs on single-CPU runners: "The container for ubuntu-slim runners runs in unprivileged mode. This means that some operations requiring elevated privileges such as mounting file systems, using Docker-in-Docker, or accessing low-level kernel features are not supported." Those low-level kernel features are what the agent needs, so monitoring inside the unprivileged container is not feasible today.

For StepSecurity enterprise customers
If your security posture requires that workflows are always monitored, you can block the use of ubuntu-slim via workflow run policies see the Runner Label Policy docs. This lets you enforce that jobs only run on monitored runner types.

New Contributors

Full Changelog: v2.19.0...v2.19.1

v2.19.0

Choose a tag to compare

@varunsh-coder varunsh-coder released this 20 Apr 07:43
Immutable release. Only release title and notes can be modified.
8d3c67d

What's Changed

New Runner Support

Harden-Runner now supports Depot, Blacksmith, Namespace, and WarpBuild runners with the same egress monitoring, runtime monitoring, and policy enforcement available on GitHub-hosted runners.

Automated Incident Response for Supply Chain Attacks

  • Global block list: Outbound connections to known malicious domains and IPs are now blocked even in audit mode.
  • System-defined detection rules: Harden-Runner will trigger lockdown mode when a high risk event is detected during an active supply chain attack (for example, a process reading the memory of the runner worker process, a common technique for stealing GitHub Actions secrets).

Bug Fixes

Windows and macOS: stability and reliability fixes

Full Changelog: v2.18.0...v2.19.0

v2.18.0

Choose a tag to compare

@varunsh-coder varunsh-coder released this 15 Apr 07:51
Immutable release. Only release title and notes can be modified.
6c3c2f2

What's Changed

Global Block List: During supply chain incidents like the recent axios and trivy compromises, StepSecurity will add known malicious domains and IP addresses (IOCs) to a global block list. These will be automatically blocked, even in audit mode, providing immediate protection without requiring any workflow changes.

Deploy on Self-Hosted VM: Added deploy-on-self-hosted-vm input that allows the Harden Runner agent to be installed directly on ephemeral self-hosted Linux runner VMs at workflow runtime. This is intended as an alternative when baking the agent into the VM image is not possible.

Full Changelog: v2.17.0...v2.18.0