Update step-security/harden-runner action to v2.11.0 #150
Conversation
Signed-off-by: Mend Renovate <[email protected]>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hello @renovate-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
Summary of Changes
This pull request updates the step-security/harden-runner GitHub Action from version v2.10.1 to v2.11.0. This action is used in the ci-lint-test.yml and ci-unit-tests.yml workflows to enhance the security of the runner environment. The update includes improvements and bug fixes as detailed in the release notes, including support for eBPF for DNS resolution and network call monitoring in the Enterprise tier, a fix for potential post-step failures, and a fix for DNS request issues with uppercase characters.
Highlights
- Dependency Update: The
step-security/harden-runneraction is updated fromv2.10.1tov2.11.0. - Security Enhancement: The update includes fixes for command injection weaknesses and improvements to container detection.
- New Feature (Enterprise): Harden-Runner Enterprise tier now supports the use of eBPF for DNS resolution and network call monitoring.
Changelog
- .github/workflows/ci-lint-test.yml
- Updates the
step-security/harden-runneraction tov2.11.0(from91182cccc01eb5e619899d80e4e971d6181294a7to4d991eb9b905ef189e4c376166672c3f2f230481) on line 45.
- Updates the
- .github/workflows/ci-unit-tests.yml
- Updates the
step-security/harden-runneraction tov2.11.0(from91182cccc01eb5e619899d80e4e971d6181294a7to4d991eb9b905ef189e4c376166672c3f2f230481) on line 24.
- Updates the
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
The runner hardens, a shield in the night,
Protecting our builds with all of its might.
From injection's sting to DNS request's call,
It watches and guards, preventing the fall.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Code Review
This PR updates the step-security/harden-runner action to v2.11.0 in the CI workflows. The update includes fixes for command injection weaknesses and improvements in DNS request handling. The changes appear straightforward and involve updating the action version in the workflow files.
Merge Readiness
The pull request updates the version of the step-security/harden-runner action in the CI workflows. Given the fixes included in the new version, this update is beneficial for security and stability. I am unable to directly approve the pull request, and recommend that others review and approve this code before merging. The changes are simple and the update seems safe to merge.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #150 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 11 11
Lines 478 478
=========================================
Hits 478 478 ☔ View full report in Codecov by Sentry. |
This PR contains the following updates:
v2.10.1->v2.11.0Release Notes
step-security/harden-runner (step-security/harden-runner)
v2.11.0Compare Source
What's Changed
Release v2.11.0 in #498
Harden-Runner Enterprise tier now supports the use of eBPF for DNS resolution and network call monitoring
Full Changelog: step-security/harden-runner@v2...v2.11.0
v2.10.4Compare Source
What's Changed
Fixed a potential Harden-Runner post step failure that could occur when printing agent service logs. The fix gracefully handles failures without failing the post step.
Full Changelog: step-security/harden-runner@v2...v2.10.4
v2.10.3Compare Source
What's Changed
Fixed an issue where DNS requests using uppercase characters (e.g., EXAMPLE.com) were blocked even when the domain was present in the allowed list. This update standardizes domain names to lowercase for consistent comparison.
Full Changelog: step-security/harden-runner@v2...v2.10.3
v2.10.2Compare Source
What's Changed
Fixes low-severity command injection weaknesses
The advisory is here: GHSA-g85v-wf27-67xc
Bug fix to improve detection of whether Harden-Runner is running in a container
Full Changelog: step-security/harden-runner@v2...v2.10.2
Configuration
📅 Schedule: Branch creation - "on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.