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:
v4.0.2
->v4.2.0
v4.1.7
->v4.2.2
v4.3.4
->v4.4.3
v1.18.0
->v1.18.2
~> 0.34
->~> 0.35
v3.25.12
->v3.27.6
v2.3.3
->v2.4.0
v2.8.1
->v2.10.2
Release Notes
actions/cache (actions/cache)
v4.2.0
Compare Source
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version
v4
orv3
as soon as possible before February 1st, 2025. (Upgrade instructions below).If you are using pinned SHAs, please use the SHAs of versions
v4.2.0
orv3.4.0
If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Read more about the change & access the migration guide: reference to the announcement.
Minor changes
Minor and patch version updates for these dependencies:
1.11.1
1.1.3
0.38.3
Full Changelog: actions/cache@v4...v4.2.0
v4.1.2
Compare Source
What's Changed
isGhes
logic by @jww3 in https://github.com/actions/cache/pull/14744.1.2
release by @Link- in https://github.com/actions/cache/pull/1477New Contributors
Full Changelog: actions/cache@v4...v4.1.2
v4.1.1
Compare Source
What's Changed
cache-hit
output by @joshmgross in https://github.com/actions/cache/pull/1467Full Changelog: actions/cache@v4.1.0...v4.1.1
v4.1.0
Compare Source
What's Changed
save-always
input by @joshmgross in https://github.com/actions/cache/pull/1452New Contributors
Full Changelog: actions/cache@v4.0.2...v4.1.0
actions/checkout (actions/checkout)
v4.2.2
Compare Source
url-helper.ts
now leverages well-known environment variables by @jww3 in https://github.com/actions/checkout/pull/1941isGhes
by @jww3 in https://github.com/actions/checkout/pull/1946v4.2.1
Compare Source
v4.2.0
Compare Source
actions/upload-artifact (actions/upload-artifact)
v4.4.3
Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v4.4.2...v4.4.3
v4.4.2
Compare Source
What's Changed
@actions/artifact
to 2.1.11 by @robherley in https://github.com/actions/upload-artifact/pull/627Full Changelog: actions/upload-artifact@v4.4.1...v4.4.2
v4.4.1
Compare Source
What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v4.4.0...v4.4.1
v4.4.0
Compare Source
v4.3.6
Compare Source
v4.3.5
Compare Source
erlef/setup-elixir (erlef/setup-elixir)
v1.18.2
Compare Source
What's Changed
Full Changelog: erlef/setup-beam@v1.18.1...v1.18.2
v1.18.1
Compare Source
What's Changed
latest
not matching internal elements by @Schultzer in https://github.com/erlef/setup-beam/pull/298Full Changelog: erlef/setup-beam@v1...v1.18.1
github/codeql-action (github/codeql-action)
v3.27.6
Compare Source
v3.27.5
Compare Source
v3.27.4
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2
andv3
of the CodeQL Action is the node version they support, withv3
running on node 20 while we continue to releasev2
to support running on node 16. For example3.22.11
was the firstv3
release and is functionally identical to2.22.11
. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.3.27.4 - 14 Nov 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.27.3
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2
andv3
of the CodeQL Action is the node version they support, withv3
running on node 20 while we continue to releasev2
to support running on node 16. For example3.22.11
was the firstv3
release and is functionally identical to2.22.11
. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.3.27.3 - 12 Nov 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.27.2
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2
andv3
of the CodeQL Action is the node version they support, withv3
running on node 20 while we continue to releasev2
to support running on node 16. For example3.22.11
was the firstv3
release and is functionally identical to2.22.11
. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.3.27.2 - 12 Nov 2024
See the full CHANGELOG.md for more information.
v3.27.1
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2
andv3
of the CodeQL Action is the node version they support, withv3
running on node 20 while we continue to releasev2
to support running on node 16. For example3.22.11
was the firstv3
release and is functionally identical to2.22.11
. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.3.27.1 - 08 Nov 2024
See the full CHANGELOG.md for more information.
v3.27.0
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2
andv3
of the CodeQL Action is the node version they support, withv3
running on node 20 while we continue to releasev2
to support running on node 16. For example3.22.11
was the firstv3
release and is functionally identical to2.22.11
. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.3.27.0 - 22 Oct 2024
upload-sarif
Action would fail with "upload-sarif post-action step failed: Input required and not supplied: token" when called in a composite Action that had a different set of inputs to the ones expected by theupload-sarif
Action. #2557See the full CHANGELOG.md for more information.
v3.26.13
Compare Source
v3.26.12
Compare Source
v3.26.11
Compare Source
v3.26.10
Compare Source
v3.26.9
Compare Source
v3.26.8
Compare Source
v3.26.7
Compare Source
v3.26.6
Compare Source
v3.26.5
Compare Source
v3.26.4
Compare Source
v3.26.3
Compare Source
v3.26.2
Compare Source
v3.26.1
Compare Source
v3.26.0
Compare Source
v3.25.15
Compare Source
v3.25.14
Compare Source
v3.25.13
Compare Source
ossf/scorecard-action (ossf/scorecard-action)
v2.4.0
Compare Source
What's Changed
This update bumps the Scorecard version to the v5 release. For a complete list of changes, please refer to the v5.0.0 release notes. Of special note to Scorecard Action is the Maintainer Annotation feature, which can be used to suppress some Code Scanning false positives. Alerts will not be generated for any Scorecard Check with an annotation.
Documentation
New Contributors
Full Changelog: ossf/scorecard-action@v2.3.3...v2.4.0
step-security/harden-runner (step-security/harden-runner)
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
Configuration
📅 Schedule: Branch creation - "* 0-3 1 * *" (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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.