Skip to content

build(deps): bump step-security/harden-runner from 2.19.0 to 2.19.4#1247

Open
dependabot[bot] wants to merge 3 commits into
masterfrom
dependabot/github_actions/step-security/harden-runner-2.19.4
Open

build(deps): bump step-security/harden-runner from 2.19.0 to 2.19.4#1247
dependabot[bot] wants to merge 3 commits into
masterfrom
dependabot/github_actions/step-security/harden-runner-2.19.4

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 25, 2026

Bumps step-security/harden-runner from 2.19.0 to 2.19.4.

Release notes

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

v2.19.4

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

v2.19.3

What's Changed

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

v2.19.2

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

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

Commits
  • 9af89fc Merge pull request #667 from step-security/update-agent-v1.8.6
  • 485dce8 Update agent to v1.8.6
  • ab7a940 Merge pull request #665 from step-security/fix/use-policy-store-default-audit
  • ec41b78 Default to audit mode when api-key missing with use-policy-store
  • 9ca718d Merge pull request #664 from step-security/update-agent-v1.8.5
  • 1dee3df Update agent to v1.8.5
  • a5ad31d Merge pull request #657 from devantler/fix/ubuntu-slim-user-env
  • 6e92856 build dist and trim ubuntu-slim message
  • 4e0504e Merge branch 'main' into fix/ubuntu-slim-user-env
  • 376d25a fix: detect ubuntu-slim runners early and bail out
  • See full diff 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)

Bumps [step-security/harden-runner](https://github.com/step-security/harden-runner) from 2.19.0 to 2.19.4.
- [Release notes](https://github.com/step-security/harden-runner/releases)
- [Commits](step-security/harden-runner@8d3c67d...9af89fc)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label May 25, 2026
mixonic added 2 commits May 26, 2026 11:44
The Run Tests CI checks failed after step-security/harden-runner
was updated from 2.19.0 to 2.19.4.

Root cause: The update to harden-runner coincided with a dependency
resolution issue where testem (which uses CommonJS require()) was
resolving to an ESM-only version of execa (v7+) in a nested node_modules
directory. This caused an ERR_REQUIRE_ESM error: "require() of ES Module
.../testem/node_modules/execa/index.js not supported."

Fix: Added a yarn resolution to force all packages to use execa@^5.1.1,
which is the latest CommonJS-compatible version. This ensures testem
gets a compatible execa version that can be loaded via require().

Risk: Low risk. execa@5.1.1 is a stable, widely-used version that
maintains CommonJS compatibility. The resolution ensures consistent
dependency resolution across all environments.

Files changed:
- package.json

Automated fix by veni-vidi-fixi
The Run Tests CI checks failed after step-security/harden-runner
was updated from 2.19.0 to 2.19.4.

Root cause: The yarn.lock file was out of sync after the GitHub Actions
dependency update. This caused ember-cli to fail during initialization
with "Cannot read properties of undefined (reading 'debug')" because
the dependency tree was not properly resolved.

Fix: Ran yarn install to regenerate yarn.lock and ensure all
dependencies are properly resolved with their transitive dependencies.

Risk: Low risk: only regenerated the lockfile to sync with the current
package.json and GitHub Actions dependencies.

Files changed:
- yarn.lock

Automated fix by veni-vidi-fixi
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

Development

Successfully merging this pull request may close these issues.

1 participant