chore(deps): update github-actions (major) #358
Merged
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:
v5.4.0
->v6.9.0
v3.7.13
->v4.1.1
v3.5.0
->v4.1.0
v1.10.0
->v2.0.2
v7.13.0
->v8.1.0
v6.1.0
->v7.0.5
22.04
->24.04
Release Notes
docker/build-push-action (docker/build-push-action)
v6.9.0
Compare Source
Full Changelog: docker/build-push-action@v6.8.0...v6.9.0
v6.8.0
Compare Source
Full Changelog: docker/build-push-action@v6.7.0...v6.8.0
v6.7.0
Compare Source
v6.6.1
Compare Source
Full Changelog: docker/build-push-action@v6.6.0...v6.6.1
v6.6.0
Compare Source
v6.5.0
Compare Source
v6.4.1
Compare Source
v6.4.0
Compare Source
repository
andghtoken
attributes for GitHub Actions cache backend by @crazy-max in https://github.com/docker/build-push-action/pull/1133Full Changelog: docker/build-push-action@v6.3.0...v6.4.0
v6.3.0
Compare Source
DOCKER_BUILD_RECORD_UPLOAD
environment variable to enable/disable build record upload by @crazy-max in https://github.com/docker/build-push-action/pull/1172DOCKER_BUILD_NO_SUMMARY
has been deprecated. SetDOCKER_BUILD_SUMMARY
tofalse
instead by @crazy-max in https://github.com/docker/build-push-action/pull/1170 https://github.com/docker/build-push-action/pull/1173Full Changelog: docker/build-push-action@v6.2.0...v6.3.0
v6.2.0
Compare Source
Full Changelog: docker/build-push-action@v6.1.0...v6.2.0
v6.1.0
Compare Source
v6.0.2
Compare Source
v6.0.1
Compare Source
v6.0.0
Compare Source
google-github-actions/release-please-action (google-github-actions/release-please-action)
v4.1.1
Compare Source
Bug Fixes
v4.1.0
Compare Source
Features
changelog-host
input toaction.yml
(#948) (863b06f)v4.0.3
Compare Source
Bug Fixes
v4.0.2
Compare Source
Bug Fixes
v4.0.1
Compare Source
Bug Fixes
v4.0.0
Compare Source
gradle/actions (gradle/actions)
v4.1.0
Compare Source
This release brings some minor improvements:
develocity-token-expiry
parameter had no effect (#381)Full Changelog: gradle/actions@v4.0.1...v4.1.0
v4.0.1
Compare Source
This patch release updates a number of dependencies, and fixes a bug that caused Gradle version '8.1' to be confused with '8.10'.
What's Changed
Full Changelog: gradle/actions@v4.0.0...v4.0.1
v4.0.0
Compare Source
Final release of
v4.0.0
of thesetup-gradle
,dependency-submission
andwrapper-validation
actions provided undergradle/actions
.This release is available under the
v4
tag.Major changes from the
v3
releaseThe
arguments
parameter has been removedUsing the action to execute Gradle via the
arguments
parameter was deprecated inv3
and this parameter has been removed.See here for more details.
Cache cleanup enabled by default
After a number of fixes and improvements, this release enables cache-cleanup by default for all Jobs using the
setup-gradle
anddependency-submission
actions.Improvements and bugfixes related cache cleanup:
This feature should help to minimize the size of entries written to the GitHub Actions cache, speeding up builds and reducing cache usage.
Wrapper validation enabled by default
In
v3
, thesetup-gradle
action was enhanced to support Gradle wrapper validation, removing the need to use a separate workflowfile with the
gradle/actions/wrapper-validation
action.With this release, wrapper validation has been significantly improved, and is now enabled by default (#12):
allow-snapshot-wrappers
makes it possible to validate snapshot wrapper jars usingsetup-gradle
.wrapper-validation
for new Gradle versions: By only fetching wrapper checksums for Gradle versions that were not known when this action was released, this release reduces the likelihood that a network failure could cause failure in wrapper validation (#171)wrapper-validation
finds no wrapper jars (#284)Wrapper validation is important for supply-chain integrity. Enabling this feature by default will increase the coverage of wrapper
validation on projects using GitHub Actions.
New input parameters for Dependency Graph generation
Some dependency-graph inputs that could previously only be configured via environment variables now have dedicated action inputs:
dependency-graph-report-dir
: sets the location where dependency-graph reports will be generateddependency-graph-exclude-projects
anddependency-graph-include-projects
: select which Gradle projects will contribute to the generated dependency graph.dependency-graph-exclude-configurations
anddependency-graph-include-configurations
: select which Gradle configurations will contribute to the generated dependency graph.Other improvements
read-only
ordisabled
(#255)setup-gradle
requests a specific Gradle version, the action will no longer download and install that version if it is already available on thePATH
of the runner (#270)setup-gradle
anddependency-submission
actions now attempt to use theD:
drive for Gradle User Home if it is available (#290)Deprecations and breaking changes
gradle-home-cache-cleanup
input parameter has been deprecated and replaced bycache-cleanup
dependency-graph: clear
parameter has been removed without replacementv3
have been removed:Changelog
Full Changelog: gradle/actions@v3.5.0...v4.0.0
lycheeverse/lychee-action (lycheeverse/lychee-action)
v2.0.2
: Version 2.0.2Compare Source
What's Changed
New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.0.2
v2.0.1
: Version 2.0.1Compare Source
What's Changed
New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.0.1
v2.0.0
: Version 2.0.0Compare Source
Breaking Changes
Note: This release improves the action's robustness by changing default behaviors. Changes are only required if you want to opt out of the new failure conditions. Most users won't need to modify their existing configurations.
Fail pipeline on error by default
We've changed the default behavior: pipelines will now fail on broken links automatically. This addresses user feedback that not failing on broken links was unexpected (see issue #71).
What you need to do:
lychee-action@master
branch don't need to make any changes, asfail: true
has been the default there for a while.fail
tofalse
when updating:Fail pipeline if no links were found
Similar to the above change, we now fail the pipeline if no links are found during a run. This helps warn users about potential configuration issues.
What you need to do:
For a more detailed description of the technical aspects behind these changes, please see the full changelog below.
What's Changed
failIfEmpty
argument (fixes #84) by @mre in https://github.com/lycheeverse/lychee-action/pull/86New Contributors
Full Changelog: lycheeverse/lychee-action@v1...v1.11.0
oxsecurity/megalinter (oxsecurity/megalinter)
v8.1.0
Compare Source
Core
New linters
Linters enhancements
--skip-db-update --skip-check-update
(not ideal but better than nothing)Fixes
Reporters
Doc
CI
pytest-rerunfailures
to improve CI control jobs success, by @AlejandroSuero in #3993Linter versions upgrades
v8.0.0
Compare Source
Removed deprecated linters, by @nvuillam in #3854
Core
output_variables
property, by @nvuillam in #3861Media
Linters enhancements
Fixes
Doc
CI
skip_checkout: true
to default MegaLinter GitHub Action templatemega-linter-runner
Linter versions upgrades
peter-evans/create-pull-request (peter-evans/create-pull-request)
v7.0.5
: Create Pull Request v7.0.5Compare Source
⚙️ Fixes an issue with commit signing to allow it to support symlinks
What's Changed
Full Changelog: peter-evans/create-pull-request@v7.0.4...v7.0.5
v7.0.4
: Create Pull Request v7.0.4Compare Source
⚙️ Fixes an issue with commit signing to allow it to support submodules
What's Changed
New Contributors
Full Changelog: peter-evans/create-pull-request@v7.0.3...v7.0.4
v7.0.3
: Create Pull Request v7.0.3Compare Source
⚙️ Fixes an issue with commit signing where commit SHAs have variable lengths when abbreviated.
What's Changed
Full Changelog: peter-evans/create-pull-request@v7.0.2...v7.0.3
v7.0.2
: Create Pull Request v7.0.2Compare Source
⚙️ Fixes an issue with commit signing when a change was detected as being a rename or copy.
What's Changed
Full Changelog: peter-evans/create-pull-request@v7.0.1...v7.0.2
v7.0.1
: Create Pull Request v7.0.1Compare Source
⚙️ Fixes an issue affecting one particular use case where the action fails on
diff --stat
withfatal: ambiguous argument
.What's Changed
Full Changelog: peter-evans/create-pull-request@v7.0.0...v7.0.1
v7.0.0
: Create Pull Request v7.0.0Compare Source
✨ Now supports commit signing with bot-generated tokens! See "What's new" below. ✍️🤖
Behaviour changes
git-token
has been renamedbranch-token
, to be more clear about its purpose. Thebranch-token
is the token that the action will use to create and update the branch.Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.