-
Notifications
You must be signed in to change notification settings - Fork 1
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.9.1 #703
Merged
myrotvorets-team
merged 1 commit into
master
from
renovate/step-security-harden-runner-2.x
Aug 23, 2024
Merged
chore(deps): update step-security/harden-runner action to v2.9.1 #703
myrotvorets-team
merged 1 commit into
master
from
renovate/step-security-harden-runner-2.x
Aug 23, 2024
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
added
dependencies
Pull requests that update a dependency file
github-actions
labels
Jul 18, 2024
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Manifest Files.github/workflows/dependency-review.yml.github/workflows/package-audit.yml |
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
5 times, most recently
from
July 25, 2024 13:04
b8abafe
to
8c00898
Compare
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
3 times, most recently
from
July 29, 2024 09:23
8a9f565
to
eabafbe
Compare
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
August 5, 2024 04:10
eabafbe
to
4d62834
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 5, 2024
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
4 times, most recently
from
August 12, 2024 03:20
cc7997f
to
6dae7f1
Compare
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
5 times, most recently
from
August 19, 2024 22:05
8ca31e5
to
59dbc65
Compare
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
August 21, 2024 21:12
59dbc65
to
1cc5bba
Compare
Quality Gate passedIssues Measures |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.8.1
->v2.9.1
Release Notes
step-security/harden-runner (step-security/harden-runner)
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
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.