[PR #7156] [MERGED] build(deps): bump step-security/harden-runner from 2.16.1 to 2.19.0 #6347

New issue

Closed

opened 2026-05-05 10:55:13 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 10:55:13 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/netblue30/firejail/pull/7156
Author: @dependabot[bot]
Created: 5/1/2026
Status: ✅ Merged
Merged: 5/1/2026
Merged by: @kmk3

Base: master ← Head: dependabot/github_actions/step-security/harden-runner-2.19.0

📝 Commits (1)

d8f1132 build(deps): bump step-security/harden-runner from 2.16.1 to 2.19.0

📊 Changes

7 files changed (+14 additions, -14 deletions)

View changed files

📝 .github/workflows/build-extra.yml (+2 -2)
📝 .github/workflows/build.yml (+1 -1)
📝 .github/workflows/check-c.yml (+3 -3)
📝 .github/workflows/check-profiles.yml (+1 -1)
📝 .github/workflows/check-python.yml (+1 -1)
📝 .github/workflows/codespell.yml (+1 -1)
📝 .github/workflows/test.yml (+5 -5)

📄 Description

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

Release notes

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

v2.19.0

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: https://github.com/step-security/harden-runner/compare/v2.18.0...v2.19.0

v2.18.0

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: https://github.com/step-security/harden-runner/compare/v2.17.0...v2.18.0

v2.17.0

What's Changed

Policy Store Support

Added use-policy-store and api-key inputs to fetch security policies directly from the StepSecurity Policy Store. Policies can be defined and attached at the workflow, repo, org, or cluster (ARC) level, with the most granular policy taking precedence. This is the preferred method over the existing policy input which requires id-token: write permission. If no policy is found in the store, the action defaults to audit mode.

Full Changelog: https://github.com/step-security/harden-runner/compare/v2.16.1...v2.17.0

Commits

8d3c67d Release v2.19.0 (#661)
6c3c2f2 Feature/deploy on self hosted vm (#658)
f808768 Feature/policy store (#656)
See full diff in compare view

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)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/netblue30/firejail/pull/7156 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 5/1/2026 **Status:** ✅ Merged **Merged:** 5/1/2026 **Merged by:** [@kmk3](https://github.com/kmk3) **Base:** `master` ← **Head:** `dependabot/github_actions/step-security/harden-runner-2.19.0` --- ### 📝 Commits (1) - [`d8f1132`](https://github.com/netblue30/firejail/commit/d8f1132b7e67c09d8e50400bb6eaba10b6d1b749) build(deps): bump step-security/harden-runner from 2.16.1 to 2.19.0 ### 📊 Changes **7 files changed** (+14 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/build-extra.yml` (+2 -2) 📝 `.github/workflows/build.yml` (+1 -1) 📝 `.github/workflows/check-c.yml` (+3 -3) 📝 `.github/workflows/check-profiles.yml` (+1 -1) 📝 `.github/workflows/check-python.yml` (+1 -1) 📝 `.github/workflows/codespell.yml` (+1 -1) 📝 `.github/workflows/test.yml` (+5 -5) </details> ### 📄 Description Bumps [step-security/harden-runner](https://github.com/step-security/harden-runner) from 2.16.1 to 2.19.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/step-security/harden-runner/releases">step-security/harden-runner's releases</a>.</em></p> <blockquote> <h2>v2.19.0</h2> <h2>What's Changed</h2> <h3>New Runner Support</h3> <p>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.</p> <h3>Automated Incident Response for Supply Chain Attacks</h3> <ul> <li>Global block list: Outbound connections to known malicious domains and IPs are now blocked even in audit mode.</li> <li>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).</li> </ul> <h3>Bug Fixes</h3> <p>Windows and macOS: stability and reliability fixes</p> <p><strong>Full Changelog</strong>: <a href="https://github.com/step-security/harden-runner/compare/v2.18.0...v2.19.0">https://github.com/step-security/harden-runner/compare/v2.18.0...v2.19.0</a></p> <h2>v2.18.0</h2> <h2>What's Changed</h2> <p>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.</p> <p>Deploy on Self-Hosted VM: Added <code>deploy-on-self-hosted-vm</code> 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.</p> <p><strong>Full Changelog</strong>: <a href="https://github.com/step-security/harden-runner/compare/v2.17.0...v2.18.0">https://github.com/step-security/harden-runner/compare/v2.17.0...v2.18.0</a></p> <h2>v2.17.0</h2> <h2>What's Changed</h2> <h3>Policy Store Support</h3> <p>Added <code>use-policy-store</code> and <code>api-key</code> inputs to fetch security policies directly from the <a href="https://docs.stepsecurity.io/harden-runner/policy-store">StepSecurity Policy Store</a>. Policies can be defined and attached at the workflow, repo, org, or cluster (ARC) level, with the most granular policy taking precedence. This is the preferred method over the existing <code>policy</code> input which requires <code>id-token: write</code> permission. If no policy is found in the store, the action defaults to audit mode.</p> <p><strong>Full Changelog</strong>: <a href="https://github.com/step-security/harden-runner/compare/v2.16.1...v2.17.0">https://github.com/step-security/harden-runner/compare/v2.16.1...v2.17.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/step-security/harden-runner/commit/8d3c67de8e2fe68ef647c8db1e6a09f647780f40"><code>8d3c67d</code></a> Release v2.19.0 (<a href="https://redirect.github.com/step-security/harden-runner/issues/661">#661</a>)</li> <li><a href="https://github.com/step-security/harden-runner/commit/6c3c2f2c1c457b00c10c4848d6f5491db3b629df"><code>6c3c2f2</code></a> Feature/deploy on self hosted vm (<a href="https://redirect.github.com/step-security/harden-runner/issues/658">#658</a>)</li> <li><a href="https://github.com/step-security/harden-runner/commit/f808768d1510423e83855289c910610ca9b43176"><code>f808768</code></a> Feature/policy store (<a href="https://redirect.github.com/step-security/harden-runner/issues/656">#656</a>)</li> <li>See full diff in <a href="https://github.com/step-security/harden-runner/compare/fe104658747b27e96e4f7e80cd0a94068e53901d...8d3c67de8e2fe68ef647c8db1e6a09f647780f40">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=step-security/harden-runner&package-manager=github_actions&previous-version=2.16.1&new-version=2.19.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

gitea-mirror

2026-05-05 10:55:13 -06:00

closed this issue
added the
pull-request
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#6347

No description provided.

Rows
Columns