Chore: Bump step-security/harden-runner from 2.19.4 to 2.20.1 - #85
Chore: Bump step-security/harden-runner from 2.19.4 to 2.20.1#85dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [step-security/harden-runner](https://github.com/step-security/harden-runner) from 2.19.4 to 2.20.1. - [Release notes](https://github.com/step-security/harden-runner/releases) - [Commits](step-security/harden-runner@9af89fc...b09bb98) --- updated-dependencies: - dependency-name: step-security/harden-runner dependency-version: 2.20.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
PR: #85 Note: This metadata is also included in the Gerrit commit message for reconciliation. |
|
Change raised in Gerrit by GitHub2Gerrit: https://gerrit.linuxfoundation.org/infra/c/releng/docs-conf/+/74618 |
|
Auto-closing pull request |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps step-security/harden-runner from 2.19.4 to 2.20.1.
Release notes
Sourced from step-security/harden-runner's releases.
Commits
b09bb98Merge pull request #680 from step-security/aws-code-build35cd77bdocs: document the Global Block List in the features listbb6dbefchore: rebuild dist with clean dependency install98f73c5chore: update eBPF agent to v1.8.1454193c1Reapply "feat(runners): detect AWS CodeBuild-hosted runners as third-party pr...d22dd48Revert "fix(self-hosted): flush agent events at job end when deploy-on-self-h...0ff0941fix(self-hosted): flush agent events at job end when deploy-on-self-hosted-vm...a3c333dRevert "feat(runners): detect AWS CodeBuild-hosted runners as third-party pro...bf94c00feat(runners): detect AWS CodeBuild-hosted runners as third-party provider514522cfix(self-hosted): resolve runner user when USER env var is unsetDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)