Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump step-security/harden-runner from 2.9.1 to 2.10.1 #9284

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 1, 2024

Bumps step-security/harden-runner from 2.9.1 to 2.10.1.

Release notes

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

v2.10.1

What's Changed

Release v2.10.1 by @​varunsh-coder in step-security/harden-runner#463 Bug fix: Resolves an issue where DNS resolution of .local domains was failing when using a Kind cluster in a GitHub Actions workflow.

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

v2.10.0

What's Changed

Release v2.10.0 by @​h0x0er and @​varunsh-coder in step-security/harden-runner#455

ARM Support: Harden-Runner Enterprise tier now supports GitHub-hosted ARM runners. This includes all the features that apply to previously supported GitHub-hosted x64 Linux runners.

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

Commits

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 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 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.9.1 to 2.10.1.
- [Release notes](https://github.com/step-security/harden-runner/releases)
- [Commits](step-security/harden-runner@5c7944e...91182cc)

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

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added backport release_3.34 On merge create a backported pull request to 3.34 dependencies Pull requests that update a dependency file labels Oct 1, 2024
@DelazJ DelazJ merged commit 7587455 into master Oct 1, 2024
6 of 8 checks passed
@dependabot dependabot bot deleted the dependabot/github_actions/step-security/harden-runner-2.10.1 branch October 1, 2024 12:12
@qgis-bot
Copy link
Collaborator

qgis-bot commented Oct 1, 2024

The backport to release_3.34 failed:

The process '/usr/bin/git' failed with exit code 1
stderr
error: could not apply fdbc3eda4b... Bump step-security/harden-runner from 2.9.1 to 2.10.1
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"

stdout
Auto-merging .github/workflows/auto-label.yml
CONFLICT (content): Merge conflict in .github/workflows/auto-label.yml
Auto-merging .github/workflows/backport.yml
CONFLICT (content): Merge conflict in .github/workflows/backport.yml
Auto-merging .github/workflows/builds.yml
CONFLICT (content): Merge conflict in .github/workflows/builds.yml
Auto-merging .github/workflows/doctest.yml
CONFLICT (content): Merge conflict in .github/workflows/doctest.yml
Auto-merging .github/workflows/pofiles.yml
CONFLICT (content): Merge conflict in .github/workflows/pofiles.yml
Auto-merging .github/workflows/pull_minimized_translations.yml
CONFLICT (content): Merge conflict in .github/workflows/pull_minimized_translations.yml
Auto-merging .github/workflows/stale.yml
CONFLICT (content): Merge conflict in .github/workflows/stale.yml
Auto-merging .github/workflows/translation_statistics.yml
CONFLICT (content): Merge conflict in .github/workflows/translation_statistics.yml

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release_3.34 release_3.34
# Navigate to the new working tree
cd .worktrees/backport-release_3.34
# Create a new branch
git switch --create backport-9284-to-release_3.34
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick fdbc3eda4b7e61f4a1799b237f163ea6498eca09
# Push it to GitHub
git push --set-upstream origin backport-9284-to-release_3.34
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release_3.34

Then, create a pull request where the base branch is release_3.34 and the compare/head branch is backport-9284-to-release_3.34.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release_3.34 On merge create a backported pull request to 3.34 dependencies Pull requests that update a dependency file failed backport
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants