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.1.2
->v4.2.0
v5.1.0
->v5.2.0
v4.5.0
->v4.6.0
v4.4.3
->v4.5.0
v3.27.0
->v3.28.0
v6.0.0
->v6.1.0
v2.10.1
->v2.11.1
v1.197.0
->v1.207.0
2.31.1
->2.32.0
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
actions/setup-go (actions/setup-go)
v5.2.0
Compare Source
What's Changed
New Contributors
Full Changelog: actions/setup-go@v5...v5.2.0
actions/setup-java (actions/setup-java)
v4.6.0
Compare Source
What's Changed
Add-ons:
Bug fixes:
New Contributors
Full Changelog: actions/setup-java@v4...v4.6.0
actions/upload-artifact (actions/upload-artifact)
v4.5.0
Compare Source
github/codeql-action (github/codeql-action)
v3.28.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.28.0 - 20 Dec 2024
See the full CHANGELOG.md for more information.
v3.27.9
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.9 - 12 Dec 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.27.8
Compare Source
v3.27.7
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.7 - 10 Dec 2024
See the full CHANGELOG.md for more information.
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.
goreleaser/goreleaser-action (goreleaser/goreleaser-action)
v6.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: goreleaser/goreleaser-action@v6.0.0...v6.1.0
r-lib/actions (r-lib/actions)
v2.11.1
Compare Source
v2.11.0
Compare Source
ruby/setup-ruby (ruby/setup-ruby)
v1.207.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.206.0...v1.207.0
v1.206.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.205.0...v1.206.0
v1.205.0
Compare Source
What's Changed
New Contributors
Full Changelog: ruby/setup-ruby@v1.204.0...v1.205.0
v1.204.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.203.0...v1.204.0
v1.203.0
Compare Source
Full Changelog: ruby/setup-ruby@v1.202.0...v1.203.0
v1.202.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.201.0...v1.202.0
v1.201.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.200.0...v1.201.0
v1.200.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.199.0...v1.200.0
v1.199.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.198.0...v1.199.0
v1.198.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.197.0...v1.198.0
shivammathur/setup-php (shivammathur/setup-php)
v2.32.0
Compare Source
Changelog
pre-installed
inphp-version
input. (#872)It will setup the pre-installed PHP version on the runner as per the docs here
https://github.com/shivammathur/setup-php?tab=readme-ov-file#github-hosted-runners. If the runner does not have a pre-installed PHP version, it will fail.
Please note: It is not recommended to use this unless you are doing something trivial, the pre-installed PHP versions on GitHub hosted runners are old patch versions.
.tool-versions
file format inphp-version-file
input. (#883)If you have an asdf .tool-versions file in your project.
For example, you can specify
.tool-versions
now in thephp-version-file
input and the action would setup the correct PHP version.COMPOSER_PROJECT_DIR
env value. (#894)Added support for
macos-15
GitHub hosted environment.Added support for
windows-2025
GitHub hosted environment.Added support for composer-dependency-analyser tool (#859, #897)
Added information on how an extension is loaded in the wiki extension lists. (#887)
https://github.com/shivammathur/setup-php/wiki
Fixed support for debug builds. (#880)
macos-12
GitHub hosted environments.Thanks @janedbal, @alexmerlin and @tillkruss for the contributions 🎉
Thanks @desrosj, @bloodynumen and @eliashaeussler for the sponsorship ❤️
For the complete list of changes, please refer to the Full Changelog
Follow for updates
Configuration
📅 Schedule: Branch creation - "before 6am on monday" in timezone Pacific/Auckland, 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.