Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump gradle/actions from 3 to 4 (#2784)
Bumps [gradle/actions](https://github.com/gradle/actions) from 3 to 4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/gradle/actions/releases">gradle/actions's releases</a>.</em></p> <blockquote> <h2>v4.0.0-rc.1</h2> <p>First release candidate for <code>v4</code> of the <code>setup-gradle</code>, <code>dependency-submission</code> and <code>wrapper-validation</code> actions provided under <code>gradle/actions</code>. This is the first release available under the <code>v4</code> tag.</p> <h2>Major changes from the <code>v3</code> release</h2> <h3>Cache cleanup enabled by default</h3> <p>After a number of fixes and improvements, this release enables <a href="https://github.com/gradle/actions/blob/v4.0.0-rc.1/docs/setup-gradle.md#configuring-cache-cleanup">cache-cleanup</a> by default for all Jobs using the <code>setup-gradle</code> and <code>dependency-submission</code> actions.</p> <p>Improvements and bugfixes related cache cleanup:</p> <ul> <li>By default, cache cleanup is not run if any Gradle build fails (<a href="https://redirect.github.com/gradle/actions/issues/71">#71</a>)</li> <li>Cache cleanup is not run after configuration-cache reuse (<a href="https://redirect.github.com/gradle/actions/issues/19">#19</a>)</li> </ul> <p>This feature should help to minimize the size of entries written to the GitHub Actions cache, speeding up builds and reducing cache usage.</p> <h3>Wrapper validation enabled by default</h3> <p>In <code>v3</code>, the <code>setup-gradle</code> action was enhanced to support Gradle wrapper validation, removing the need to use a separate workflow file with the <code>gradle/actions/wrapper-validation</code> action.</p> <p>With this release, wrapper validation has been significantly improved, and is now enabled by default (<a href="https://redirect.github.com/gradle/actions/issues/12">#12</a>):</p> <ul> <li>The <code>allow-snapshot-wrappers</code> makes it possible to validate snapshot wrapper jars using <code>setup-gradle</code>.</li> <li>Checksums for <a href="https://services.gradle.org/distributions-snapshots/">nightly and snapshot Gradle versions</a> are now validated (<a href="https://redirect.github.com/gradle/actions/issues/281">#281</a>).</li> <li>Valid wrapper checksums are cached in Gradle User Home, reducing the need to retrieve checksum values remotely (<a href="https://redirect.github.com/gradle/actions/issues/172">#172</a>).</li> <li>Reduce network calls in <code>wrapper-validation</code> 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 (<a href="https://redirect.github.com/gradle/actions/issues/171">#171</a>)</li> <li>Improved error message when <code>wrapper-validation</code> finds no wrapper jars (<a href="https://redirect.github.com/gradle/actions/issues/284">#284</a>)</li> </ul> <p>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.</p> <h3>New input parameters for Dependency Graph generation</h3> <p>Some dependency-graph inputs that could previously only be configured via environment variables now have dedicated action inputs:</p> <ul> <li><code>dependency-graph-report-dir</code>: sets the location where dependency-graph reports will be generated</li> <li><code>dependency-graph-exclude-projects</code> and <code>dependency-graph-include-projects</code>: <a href="https://github.com/gradle/actions/blob/v4.0.0-rc.1/docs/dependency-submission.md#selecting-gradle-projects-that-will-contribute-to-the-dependency-graph">select which Gradle projects will contribute to the generated dependency graph</a>.</li> <li><code>dependency-graph-exclude-configurations</code> and <code>dependency-graph-include-configurations</code>: <a href="https://github.com/gradle/actions/blob/v4.0.0-rc.1/docs/dependency-submission.md#selecting-gradle-configurations-that-will-contribute-to-the-dependency-graph">select which Gradle configurations will contribute to the generated dependency graph</a>.</li> </ul> <h3>Other improvements</h3> <ul> <li>In Job summary, the action now provides an explanation when cache is set to <code>read-only</code> or <code>disabled</code> (<a href="https://redirect.github.com/gradle/actions/issues/255">#255</a>)</li> <li>When <code>setup-gradle</code> requests a specific Gradle version, the action will no longer download and install that version if it is already available on the <code>PATH</code> of the runner (<a href="https://redirect.github.com/gradle/actions/issues/270">#270</a>)</li> <li>To attempt to speed up builds, the <code>setup-gradle</code> and <code>dependency-submission</code> actions now attempt to use the <code>D:</code> drive for Gradle User Home if it is available (<a href="https://redirect.github.com/gradle/actions/issues/290">#290</a>)</li> </ul> <h2>Deprecations and breaking changes</h2> <ul> <li>The <code>gradle-home-cache-cleanup</code> input parameter has been deprecated and replaced by <code>cache-cleanup</code></li> <li>The undocumented <code>dependency-graph: clear</code> parameter has been removed without replacement</li> <li>The following parameters deprecated in <code>v3</code> have been removed: <ul> <li><a href="https://github.com/gradle/actions/blob/v4.0.0-rc.1/docs/deprecation-upgrade-guide.md#using-the-action-to-execute-gradle-via-the-arguments-parameter-is-deprecated">arguments</a></li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gradle/actions/commit/af1da67850ed9a4cedd57bfd976089dd991e2582"><code>af1da67</code></a> Prevent concurrent jobs in integ-test-full</li> <li><a href="https://github.com/gradle/actions/commit/f8ba43cf0a1c6e996f549846c276d916fd1abed7"><code>f8ba43c</code></a> Better names for suite workflows</li> <li><a href="https://github.com/gradle/actions/commit/bcd07e664348acd3e5608b76ae50fafdafb132a8"><code>bcd07e6</code></a> Refactor integ-tests into suites</li> <li><a href="https://github.com/gradle/actions/commit/d74ee73e9fde0bd01790c57663226b6c0bd00b71"><code>d74ee73</code></a> Refactor integ-tests</li> <li><a href="https://github.com/gradle/actions/commit/fb2e6938b6b7880b717c600941adc095478e1c0b"><code>fb2e693</code></a> [bot] Update dist directory</li> <li><a href="https://github.com/gradle/actions/commit/07190022f89d9c990a8538df18bdc064521a3c2e"><code>0719002</code></a> Improve error messages for min-wrapper-count (<a href="https://redirect.github.com/gradle/actions/issues/321">#321</a>)</li> <li><a href="https://github.com/gradle/actions/commit/ac3aebda9366152f36e8b32e05ecf218b697ccc2"><code>ac3aebd</code></a> Improve error messages for min-wrapper-count</li> <li><a href="https://github.com/gradle/actions/commit/d473db0899e318d4c0009c675a9297d84d212848"><code>d473db0</code></a> Add tests for wrapper-validation with insufficient wrappers</li> <li><a href="https://github.com/gradle/actions/commit/833b05f3e67d2b356ca3c711ce1e889efdb8d28b"><code>833b05f</code></a> [bot] Update dist directory</li> <li><a href="https://github.com/gradle/actions/commit/06905c7a0f6f95237e50bd516e8558144c1dff83"><code>06905c7</code></a> Enable wrapper-validation by default in setup-gradle (<a href="https://redirect.github.com/gradle/actions/issues/318">#318</a>)</li> <li>Additional commits viewable in <a href="https://github.com/gradle/actions/compare/v3...v4">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=gradle/actions&package-manager=github_actions&previous-version=3&new-version=4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Loading branch information