Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
build(deps): bump step-security/harden-runner from 2.7.1 to 2.8.0 in …
…the actions group (#363) Bumps the actions group with 1 update: [step-security/harden-runner](https://github.com/step-security/harden-runner). Updates `step-security/harden-runner` from 2.7.1 to 2.8.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.8.0</h2> <h2>What's Changed</h2> <p>Release v2.8.0 by <a href="https://github.com/h0x0er"><code>@h0x0er</code></a> and <a href="https://github.com/varunsh-coder"><code>@varunsh-coder</code></a> in <a href="https://redirect.github.com/step-security/harden-runner/pull/416">step-security/harden-runner#416</a> This release includes:</p> <ul> <li>File Monitoring Enhancements: Adds the capability to view the name and path of every file written during the build process.</li> <li>Process Tracking Enhancements: Adds the capability to view process names and arguments of processes run during the build process.</li> </ul> <p>These enhancements are based on insights from the XZ Utils incident, aimed at improving observability and detections during the build process.</p> <p><strong>Full Changelog</strong>: <a href="https://github.com/step-security/harden-runner/compare/v2...v2.8.0">https://github.com/step-security/harden-runner/compare/v2...v2.8.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/step-security/harden-runner/commit/f086349bfa2bd1361f7909c78558e816508cdc10"><code>f086349</code></a> Merge pull request <a href="https://redirect.github.com/step-security/harden-runner/issues/416">#416</a> from step-security/rc-8</li> <li><a href="https://github.com/step-security/harden-runner/commit/b9c325d8cec96c3cecd4f8c5ab6b4f9058e4c586"><code>b9c325d</code></a> Update image</li> <li><a href="https://github.com/step-security/harden-runner/commit/808a771f66e13e2991bc3b6062649d248f41f7b6"><code>808a771</code></a> Add info about file and process events</li> <li><a href="https://github.com/step-security/harden-runner/commit/71714298b4c48ff29a5e1a00d4e7a986f8b3beab"><code>7171429</code></a> Update agent</li> <li><a href="https://github.com/step-security/harden-runner/commit/9ff9d14760a73102d9fa2f47131624137f50ead8"><code>9ff9d14</code></a> Merge pull request <a href="https://redirect.github.com/step-security/harden-runner/issues/406">#406</a> from step-security/dependabot/github_actions/step-sec...</li> <li><a href="https://github.com/step-security/harden-runner/commit/ac5fa0194e5c1f994c09fb151efeb386a2486859"><code>ac5fa01</code></a> Bump step-security/harden-runner from 2.7.0 to 2.7.1</li> <li>See full diff in <a href="https://github.com/step-security/harden-runner/compare/a4aa98b93cab29d9b1101a6143fb8bce00e2eac4...f086349bfa2bd1361f7909c78558e816508cdc10">compare view</a></li> </ul> </details> <br /> [](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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Loading branch information
1 parent
452cf67
commit 7115386