dependabot[bot] opened a new pull request, #435: URL: https://github.com/apache/grails-intellij-plugin/pull/435
Bumps [gradle/actions/setup-gradle](https://github.com/gradle/actions) from 6.3.0 to 6.4.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/gradle/actions/releases";>gradle/actions/setup-gradle's releases</a>.</em></p> <blockquote> <h2>v6.4.0</h2> <h2>Highlights</h2> <h3>Gradle version support status in the Job Summary</h3> <p>The actions now report the support status of every Gradle version used in a workflow, as job annotations and in the Job Summary (<a href="https://redirect.github.com/gradle/actions/issues/1057";>#1057</a>). Thanks to <a href="https://github.com/ov7a";><code>@ov7a</code></a> for the contribution.</p> <table> <thead> <tr> <th>version kind</th> <th>job annotation</th> <th>version table</th> <th>below the table</th> </tr> </thead> <tbody> <tr> <td><strong>End-of-life</strong> — two or more major versions behind the latest release</td> <td>warning</td> <td>:warning:</td> <td>expandable section naming the affected release lines, pointing at the <a href="https://gradle.org/security-subscription/";>Gradle Security Subscription</a></td> </tr> <tr> <td><strong>Out of date</strong> — one major behind, or more than two minors behind on the current major</td> <td>notice</td> <td>:information_source:</td> <td>one-line legend pointing at the <a href="https://docs.gradle.org/current/userguide/feature_lifecycle.html#eol_support";>Gradle release lifecycle</a> docs</td> </tr> <tr> <td><strong>Current</strong></td> <td>none</td> <td>—</td> <td>—</td> </tr> </tbody> </table> <p>Deliberately <em>not</em> reported: patch releases (being on <code>9.7.0</code> when <code>9.7.1</code> exists is not flagged) and pre-releases (release candidates, milestones and snapshots never produce annotations). The latest Gradle release is determined from the wrapper checksum data already bundled with the action, so no network access is required.</p> <p>Note that these annotations are emitted independently of the <code>add-job-summary</code> setting: setting <code>add-job-summary: 'never'</code> suppresses the Job Summary itself, but the warning and notice annotations remain.</p> <h3>Gradle itself is now reported in the dependency graph</h3> <p>The <code>dependency-submission</code> action now applies <strong>v1.5.0</strong> of the <a href="https://github.com/gradle/github-dependency-graph-gradle-plugin";>GitHub Dependency Graph Gradle Plugin</a> (up from v1.4.2) (<a href="https://redirect.github.com/gradle/actions/issues/1069";>#1069</a>).</p> <p>The headline change is that the Gradle Build Tool running the build is now reported as an <code>org.gradle:gradle-core</code> dependency, so that <strong>GitHub can surface known vulnerabilities in the version of Gradle used to run your build</strong>. These are the coordinates that GitHub advisories for the Gradle Build Tool are published against.</p> <p>Details worth knowing:</p> <ul> <li>The entry is always reported as a <strong>direct</strong> dependency with <strong>development</strong> scope.</li> <li>It is <strong>not</strong> affected by the project, configuration or scope filters, so it appears even in graphs that filter aggressively.</li> <li>Expect dependency graphs to gain this one new entry the first time a build runs after upgrading.</li> </ul> <h3>A new Gradle signing key, if you use dependency verification</h3> <blockquote> <p>[!IMPORTANT] If your build has <a href="https://docs.gradle.org/current/userguide/dependency_verification.html#sec:signature-verification";>dependency verification</a> enabled, you must add a <strong>second</strong> trusted key before upgrading, or Dependency Graph generation will fail signature verification.</p> </blockquote> <p><code>github-dependency-graph-gradle-plugin</code> <code>1.5.0</code> is signed with a new Gradle signing subkey, and the key previously documented in our setup guide has been revoked upstream:</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gradle/actions/commit/3f5f9adaf7d9fecd50b5935e54106014257a94e6";><code>3f5f9ad</code></a> Document the new Gradle signing key for dependency verification (<a href="https://redirect.github.com/gradle/actions/issues/1071";>#1071</a>)</li> <li><a href="https://github.com/gradle/actions/commit/b031f6d1a92a4611986643414591f8f649182940";><code>b031f6d</code></a> [bot] Update dist directory</li> <li><a href="https://github.com/gradle/actions/commit/5bc4175609b5adc59007637c78e2eb52125bea3d";><code>5bc4175</code></a> Bump dependency-graph-gradle-plugin to 1.5.0 (<a href="https://redirect.github.com/gradle/actions/issues/1069";>#1069</a>)</li> <li><a href="https://github.com/gradle/actions/commit/f3ff59b4e4151fd189d67647ccb7b78ddde26db9";><code>f3ff59b</code></a> Combined automated updates: wrapper checksums, npm dependencies, setup-java (...</li> <li><a href="https://github.com/gradle/actions/commit/7927085475f60c9d4b43880590e265597c31d8b4";><code>7927085</code></a> Update .tool-versions: node 24.18.0, gradle 9.7.1, java 17 (<a href="https://redirect.github.com/gradle/actions/issues/1068";>#1068</a>)</li> <li><a href="https://github.com/gradle/actions/commit/c3897a4e73a8f23b849f1980944785e7ae34c471";><code>c3897a4</code></a> [bot] Update dist directory</li> <li><a href="https://github.com/gradle/actions/commit/6b92be19055d28f8f52e00bd24bb215841656af4";><code>6b92be1</code></a> Update dependencies (<a href="https://redirect.github.com/gradle/actions/issues/1065";>#1065</a>)</li> <li><a href="https://github.com/gradle/actions/commit/0d208da0581aab8a4c6c02b69957a02c7806bca8";><code>0d208da</code></a> [bot] Update dist directory</li> <li><a href="https://github.com/gradle/actions/commit/e49d0a36a8651e7efb23918f4532fe1d4f46de77";><code>e49d0a3</code></a> Report EOL and maintenance status for Gradle versions (<a href="https://redirect.github.com/gradle/actions/issues/1057";>#1057</a>)</li> <li><a href="https://github.com/gradle/actions/commit/575435b1ea5344b0885c3387acd4752bca7a57b7";><code>575435b</code></a> Use the root-qualified <code>:wrapper</code> task (<a href="https://redirect.github.com/gradle/actions/issues/1064";>#1064</a>)</li> <li>Additional commits viewable in <a href="https://github.com/gradle/actions/compare/9c971963bec38e04b3d30dcc455b5382be2fdbfb...3f5f9adaf7d9fecd50b5935e54106014257a94e6";>compare view</a></li> </ul> </details> <br /> [](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 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> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
