-
Notifications
You must be signed in to change notification settings - Fork 4
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
chore(deps): update step-security/harden-runner action to v2.10.4 #95
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/step-security-harden-runner-2.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
2 times, most recently
from
April 7, 2024 23:15
b1d9ed1
to
eb9095a
Compare
renovate
bot
changed the title
chore(deps): update step-security/harden-runner action to v2.7.0
chore(deps): update step-security/harden-runner action to v2.7.1
Apr 29, 2024
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
April 29, 2024 22:34
eb9095a
to
18f0d2f
Compare
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
May 22, 2024 06:23
18f0d2f
to
bdf7932
Compare
renovate
bot
changed the title
chore(deps): update step-security/harden-runner action to v2.7.1
chore(deps): update step-security/harden-runner action to v2.8.0
May 22, 2024
renovate
bot
changed the title
chore(deps): update step-security/harden-runner action to v2.8.0
chore(deps): update step-security/harden-runner action to v2.8.1
Jun 7, 2024
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
June 7, 2024 18:14
bdf7932
to
5e59288
Compare
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
July 18, 2024 21:14
5e59288
to
d7a2fba
Compare
renovate
bot
changed the title
chore(deps): update step-security/harden-runner action to v2.8.1
chore(deps): update step-security/harden-runner action to v2.9.0
Jul 18, 2024
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
August 6, 2024 02:00
d7a2fba
to
84dd06d
Compare
renovate
bot
changed the title
chore(deps): update step-security/harden-runner action to v2.9.0
chore(deps): update step-security/harden-runner action to v2.9.1
Aug 6, 2024
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
September 11, 2024 00:10
84dd06d
to
dcf7104
Compare
renovate
bot
changed the title
chore(deps): update step-security/harden-runner action to v2.9.1
chore(deps): update step-security/harden-runner action to v2.10.0
Sep 11, 2024
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
September 11, 2024 07:35
dcf7104
to
2ed53e3
Compare
renovate
bot
changed the title
chore(deps): update step-security/harden-runner action to v2.10.0
chore(deps): update step-security/harden-runner action to v2.10.1
Sep 11, 2024
renovate
bot
changed the title
chore(deps): update step-security/harden-runner action to v2.10.1
chore(deps): update step-security/harden-runner action to v2.10.2
Nov 18, 2024
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
November 18, 2024 21:48
2ed53e3
to
b820c14
Compare
renovate
bot
changed the title
chore(deps): update step-security/harden-runner action to v2.10.2
chore(deps): update step-security/harden-runner action to v2.10.3
Jan 9, 2025
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
January 9, 2025 22:45
b820c14
to
8af458b
Compare
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
January 20, 2025 01:13
8af458b
to
5c90a9b
Compare
renovate
bot
changed the title
chore(deps): update step-security/harden-runner action to v2.10.3
chore(deps): update step-security/harden-runner action to v2.10.4
Jan 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v2.6.1
->v2.10.4
Release Notes
step-security/harden-runner (step-security/harden-runner)
v2.10.4
Compare 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.3
Compare 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.2
Compare 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
v2.10.1
Compare Source
What's Changed
Release v2.10.1 by @varunsh-coder in https://github.com/step-security/harden-runner/pull/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
Compare Source
What's Changed
Release v2.10.0 by @h0x0er and @varunsh-coder in https://github.com/step-security/harden-runner/pull/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
v2.9.1
Compare Source
What's Changed
Release v2.9.1 by @h0x0er and @varunsh-coder in #440
This release includes two changes:
Full Changelog: step-security/harden-runner@v2...v2.9.1
v2.9.0
Compare Source
What's Changed
Release v2.9.0 by @h0x0er and @varunsh-coder in https://github.com/step-security/harden-runner/pull/435
This release includes:
For the enterprise tier, this change helps overcome size constraints, allowing for more reliable telemetry uploads from the Harden-Runner agent to the StepSecurity backend API. No configuration change is needed to enable this.
The Harden-Runner agent now uses a per-job key to authenticate to the StepSecurity backend API to submit telemetry. This change prevents the submission of telemetry data anonymously for a given job, improving the integrity of the data collection process. No configuration change is needed to enable this.
A Table of Contents has been added to the README file to improve navigation. This makes it easier for users to find the information they need quickly.
Updated the
braces
npm package dependency to a non-vulnerable version. The vulnerability inbraces
did not affect the Harden Runner ActionFull Changelog: step-security/harden-runner@v2...v2.9.0
v2.8.1
Compare Source
What's Changed
The previous implementation incorrectly identified large GitHub-hosted runners as self-hosted runners. As a result, harden-runner was not executing on these large GitHub-hosted runners.
Full Changelog: step-security/harden-runner@v2...v2.8.1
v2.8.0
Compare Source
What's Changed
Release v2.8.0 by @h0x0er and @varunsh-coder in https://github.com/step-security/harden-runner/pull/416
This release includes:
These enhancements are based on insights from the XZ Utils incident, aimed at improving observability and detections during the build process.
Full Changelog: step-security/harden-runner@v2...v2.8.0
v2.7.1
Compare Source
What's Changed
Release v2.7.1 by @varunsh-coder, @h0x0er, @ashishkurmi in https://github.com/step-security/harden-runner/pull/397
This release:
Full Changelog: step-security/harden-runner@v2.7.0...v2.7.1
v2.7.0
Compare Source
What's Changed
Release 2.7.0 by @varunsh-coder and @h0x0er in https://github.com/step-security/harden-runner/pull/376
This release:
Full Changelog: step-security/harden-runner@v2...v2.7.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.