Skip to content

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

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

chore(deps): update step-security/harden-runner action to v2.19.3#268
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/step-security-harden-runner-2.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 2, 2026

This PR contains the following updates:

Package Type Update Change
step-security/harden-runner action patch v2.19.0v2.19.3

Release Notes

step-security/harden-runner (step-security/harden-runner)

v2.19.3

Compare Source

What's Changed

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

v2.19.2

Compare Source

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

Full Changelog: step-security/harden-runner@v2.19.1...v2.19.2

v2.19.1

Compare Source

What's Changed

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: step-security/harden-runner@v2.19.0...v2.19.1


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 is behind base branch, 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.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@renovate renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from 0a0d4d4 to e05ff47 Compare May 13, 2026 21:38
@renovate renovate Bot changed the title chore(deps): update step-security/harden-runner action to v2.19.1 chore(deps): update step-security/harden-runner action to v2.19.2 May 13, 2026
@renovate renovate Bot force-pushed the renovate/step-security-harden-runner-2.x branch from e05ff47 to 4e1ef46 Compare May 15, 2026 01:34
@renovate renovate Bot changed the title chore(deps): update step-security/harden-runner action to v2.19.2 chore(deps): update step-security/harden-runner action to v2.19.3 May 15, 2026
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