-
Notifications
You must be signed in to change notification settings - Fork 625
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
ci(action): update step-security/harden-runner action to v2.10.1 #882
Merged
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
changed the title
ci(action): update step-security/harden-runner action to v2.7.1
ci(action): update step-security/harden-runner action to v2.8.0
May 22, 2024
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
May 22, 2024 11:46
8ce6d57
to
5f588d5
Compare
renovate
bot
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
June 7, 2024 15:03
5f588d5
to
f1a4817
Compare
renovate
bot
changed the title
ci(action): update step-security/harden-runner action to v2.8.0
ci(action): 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
July 18, 2024 22:49
f1a4817
to
0084ae7
Compare
renovate
bot
changed the title
ci(action): update step-security/harden-runner action to v2.8.1
ci(action): 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 5, 2024 23:05
0084ae7
to
38a2076
Compare
renovate
bot
changed the title
ci(action): update step-security/harden-runner action to v2.9.0
ci(action): 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
from
September 11, 2024 00:50
38a2076
to
361761d
Compare
renovate
bot
changed the title
ci(action): update step-security/harden-runner action to v2.9.1
ci(action): 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 06:22
361761d
to
5796372
Compare
renovate
bot
changed the title
ci(action): update step-security/harden-runner action to v2.10.0
ci(action): update step-security/harden-runner action to v2.10.1
Sep 11, 2024
intcreator
force-pushed
the
renovate/step-security-harden-runner-2.x
branch
from
November 6, 2024 23:55
5796372
to
39932ca
Compare
intcreator
approved these changes
Nov 6, 2024
🎉 This PR is included in version 3.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
intcreator
pushed a commit
that referenced
this pull request
Nov 12, 2024
## [3.2.0](v3.1.9...v3.2.0) (2024-11-12) ### ✨ Features * add support for Node v22 ([#914](#914)) ([9147b20](9147b20)) ### ⚙️ Continuous Integrations * **action:** update actions/checkout action to v4.2.2 ([#880](#880)) ([293f54a](293f54a)) * **action:** update actions/checkout digest to 11bd719 ([#879](#879)) ([0287c69](0287c69)) * **action:** update actions/setup-node digest to 39370e3 ([#889](#889)) ([0f7a3aa](0f7a3aa)) * **action:** update actions/upload-artifact action to v4.4.3 ([#878](#878)) ([226ad5b](226ad5b)) * **action:** update step-security/harden-runner action to v2.10.1 ([#882](#882)) ([b09438e](b09438e)) ### ♻️ Chores * **deps:** lock file maintenance ([ad613cb](ad613cb)) * **deps:** update dependency [@fast-check](https://github.com/fast-check)/jest to v2.0.3 ([2d00739](2d00739)) * **deps:** update dependency [@semantic-release](https://github.com/semantic-release)/github to v11.0.1 ([a17bbdd](a17bbdd)) * **deps:** update dependency [@types](https://github.com/types)/node to v20.17.6 ([4509c4d](4509c4d)) * **deps:** update dependency husky to v9 ([#844](#844)) ([9ea2216](9ea2216))
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.7.0
->v2.10.1
Release Notes
step-security/harden-runner (step-security/harden-runner)
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
Configuration
📅 Schedule: Branch creation - "before 5am every weekday,every weekend" (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.