This release should vastly reduce the number of network requests made by the wrapper-validation-action, by hardcoding the checksums of all known Gradle wrapper jars at time of release. With this improvement, a number of long-standing issues should be addressed (#164, #162, #57).
The action should now only make network requests to validate the checksums of an unknown gradle-wrapper.jar. This can happen if:
The Gradle version was published after this action was released
The gradle-wrapper.jar is truly invalid
Changelog
[NEW] Hardcode list of known checksums to avoid network requests in most cases (#161)
Huge thanks to @Marcono1234 for contributing this long-awaited improvement.
v2.0.1
This patch release fixes error reporting when failing to retrieve the checksums from services.gradle.org
[FIX] After migration from v1 to v2 silently fails (#174)
v2.0.0
What's Changed
The version of the Node.js runtime was updated to 20, and the majority of dependencies were updated to the latest versions.
From now on, the wrapper-validation-action will require a Node.js 20 runtime environment.
There are no functional changes in this release.
This release is tagged with the v2 version label.
This is a release candidate for v2.0.0. It is also available under the v2 version label.
What's Changed
The version of the Node.js runtime was updated to 20, and the majority of dependencies were updated to the latest versions.
From now on, the wrapper-validation-action will require a Node.js 20 runtime environment.
This is the first release of gradle/gradle-build-action available with the v3 version tag.
[!IMPORTANT]
As of v3 this action has been superceded by gradle/actions/setup-gradle.
Any workflow that uses gradle/gradle-build-action@v3 will transparently delegate to gradle/actions/setup-gradle@v3.
Users are encouraged to update their workflows, replacing:
The only major breaking change from gradle-build-action@v2.12.0 is the update to require a Node 20 runtime environment.
Aside from that change, this release should generally serve as a drop-in replacement for gradle-build-action@v2.
[NEW] - Added dependency-graph-continue-on-failure input, which can be set to false to force the Job to fail when dependency graph submission fails (gradle/gradle-build-action#1036). Failure modes include:
Fail build step if version of Gradle being executed is not supported for dependency-graph generation (gradle/gradle-build-action#1034)
Fail job if permissions are insufficient to submit dependency graph via Dependency Submission API (gradle/gradle-build-action#997)
[NEW] - Add dependency-graph: clear option to clear any dependency-graph previously submitted by the job
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
Bumps the github-actions group with 2 updates: gradle/wrapper-validation-action and gradle/gradle-build-action.
Updates
gradle/wrapper-validation-action
from 1.1.0 to 2.1.1Release notes
Sourced from gradle/wrapper-validation-action's releases.
Commits
699bb18
Build outputs69d55fa
Update known wrapper checksumse636552
Bump the npm-dependencies group with 1 update85cde3f
Add clarification about running in repository root8a2cbc9
Clarify that wrapper-validation should precede setup-gradled355de3
Build outputsac96f18
Hardcoded checksums follow-upca85ed0
Extend integration testsc4ee1cd
Update known wrapper checksumsa3555ef
Clarify output format (#177)Updates
gradle/gradle-build-action
from 2 to 3Release notes
Sourced from gradle/gradle-build-action's releases.
... (truncated)
Commits
3b1b3b9
Prepare for v3.0.0 released4bd442
Delegate to 'setup-gradle@v3.0.0-rc.2'4587492
Redirect some README contentef85c4e
Bump DV plugin version to 3.16.27e08fe2
Run full-check on change to action.yml4a8703f
Delegate to 'setup-gradle@v3.0.0-rc.1'4a39eed
Mention setup-gradle in README272883a
Remove all action sources: these have been migrated to 'gradle/actions'2a8bfcf
Delegate action implementation to gradle/actions/setup-gradlee1ada08
Bump the github-actions group with 1 update (#1047)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show