[dependabot]

Bumps the actions group with 3 updates in the / directory: gradle/actions/setup-gradle, softprops/action-gh-release and gradle/actions/wrapper-validation.

Updates gradle/actions/setup-gradle from 6.3.0 to 6.4.1

Release notes

Sourced from gradle/actions/setup-gradle's releases.

v6.4.1

Security fix

This release fixes a security vulnerability in the dependency-submission action: GHSA-chpw-2mqm-95cc. All users should upgrade.

What's Changed

• Combined dependency updates by @​bigdaz in gradle/actions#1105
• Update to latest Dependency Graph plugin by @​bigdaz in gradle/actions#1106

Full Changelog: gradle/actions@v6.4.0...v6.4.1

v6.4.0

Highlights

Gradle version support status in the Job Summary

The actions now report the support status of every Gradle version used in a workflow, as job annotations and in the Job Summary (#1057). Thanks to @​ov7a for the contribution.

version kind	job annotation	version table	below the table
End-of-life — two or more major versions behind the latest release	warning	⚠️	expandable section naming the affected release lines, pointing at the Gradle Security Subscription
Out of date — one major behind, or more than two minors behind on the current major	notice	ℹ️	one-line legend pointing at the Gradle release lifecycle docs
Current	none	—	—

Deliberately not reported: patch releases (being on 9.7.0 when 9.7.1 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.

Note that these annotations are emitted independently of the add-job-summary setting: setting add-job-summary: 'never' suppresses the Job Summary itself, but the warning and notice annotations remain.

Gradle itself is now reported in the dependency graph

The dependency-submission action now applies v1.5.0 of the GitHub Dependency Graph Gradle Plugin (up from v1.4.2) (#1069).

The headline change is that the Gradle Build Tool running the build is now reported as an org.gradle:gradle-core dependency, so that GitHub can surface known vulnerabilities in the version of Gradle used to run your build. These are the coordinates that GitHub advisories for the Gradle Build Tool are published against.

Details worth knowing:

• The entry is always reported as a direct dependency with development scope.
• It is not affected by the project, configuration or scope filters, so it appears even in graphs that filter aggressively.

... (truncated)

Commits

• 8da46b5 [bot] Update dist directory
• dcf6f72 Merge commit from fork
• bf74269 Update to latest Dependency Graph plugin (#1106)
• 65a6ba9 [bot] Update dist directory
• 35eba4f Combined dependency updates (#1105)
• 1cff18a Update known wrapper checksums (#1075)
• 399f0d3 Update known wrapper checksums
• ecf8cf2 Bump references to Develocity Gradle plugin from 4.5.1 to 4.6.0 (#1080)
• d740e82 Bump references to Develocity Gradle plugin from 4.5.1 to 4.6.0
• f9f39a9 Bump references to Develocity Gradle plugin from 4.5.0 to 4.5.1 (#1072)
• Additional commits viewable in compare view

Updates softprops/action-gh-release from 3.0.3 to 3.0.4

Release notes

Sourced from softprops/action-gh-release's releases.

v3.0.4

• maintenance release with updated dependencies

Changelog

Sourced from softprops/action-gh-release's changelog.

3.0.4

• maintenance release with updated dependencies

3.0.3

3.0.3 is a maintenance release with updated dependencies. It also safely classifies malformed GitHub API errors to avoid secondary failures (#822).

What's Changed

Bug fixes 🐛

• fix: safely classify GitHub API errors by @​chenrui333 in softprops/action-gh-release#822

Other Changes 🔄

• dependency updates

3.0.2

3.0.2 is a patch release focused on release reliability and compatibility. It reuses existing draft releases when publishing prereleases, supports replacing release assets on Gitea, hardens streamed asset uploads, and provides clearer release-creation diagnostics. It also includes TypeScript, coverage, and tooling maintenance merged since 3.0.1.

This release fixes #795, #438, and #803. The upload transport hardening covers the historical failure reported in #790, although current hosted Node 24 runners did not reproduce it naturally. The diagnostics work is related to #786 and does not claim a reproducible release-creation fix.

What's Changed

Exciting New Features 🎉

• feat: improve release error reporting and test coverage by @​chenrui333 in softprops/action-gh-release#813

Bug fixes 🐛

• fix: publish existing draft releases as prereleases by @​godfengliang in softprops/action-gh-release#801
• fix: upload small checksum assets reliably by @​chenrui333 in softprops/action-gh-release#815
• fix: replace existing release assets on Gitea by @​chenrui333 in softprops/action-gh-release#816
• fix: clarify release creation 404 errors by @​chenrui333 in softprops/action-gh-release#817

Other Changes 🔄

• chore(deps): upgrade TypeScript to 7 by @​chenrui333 in softprops/action-gh-release#812
• chore(deps): remove unused TypeScript tooling by @​chenrui333 in softprops/action-gh-release#814
• dependency, Node 24 pin, and CI maintenance merged since 3.0.1

... (truncated)

Commits

• 8a0cd65 release 3.0.4 (#865)
• ac01154 chore(deps): bump the npm group across 1 directory with 4 updates (#864)
• ca4c9d5 chore(deps): bump minimatch and glob (#862)
• e4a57ae chore(deps): bump undici from 6.29.0 to 6.29.1 (#859)
• ee55a0e chore(deps): bump vite from 8.3.2 to 8.3.5 (#855)
• 8d42b22 chore(deps): bump actions/setup-node (#853)
• 6680cc0 chore(deps): bump the npm group with 3 updates (#851)
• 4a050ba chore(deps): bump source-map-js from 1.2.1 to 1.2.2 (#850)
• b5a645e chore(deps): bump the npm group with 4 updates (#848)
• d99a5de chore(deps): bump brace-expansion from 5.0.9 to 5.0.12 (#846)
• Additional commits viewable in compare view

Updates gradle/actions/wrapper-validation from 6.3.0 to 6.4.1

Release notes

Sourced from gradle/actions/wrapper-validation's releases.

v6.4.1

Security fix

This release fixes a security vulnerability in the dependency-submission action: GHSA-chpw-2mqm-95cc. All users should upgrade.

What's Changed

• Combined dependency updates by @​bigdaz in gradle/actions#1105
• Update to latest Dependency Graph plugin by @​bigdaz in gradle/actions#1106

Full Changelog: gradle/actions@v6.4.0...v6.4.1

v6.4.0

Highlights

Gradle version support status in the Job Summary

The actions now report the support status of every Gradle version used in a workflow, as job annotations and in the Job Summary (#1057). Thanks to @​ov7a for the contribution.

version kind	job annotation	version table	below the table
End-of-life — two or more major versions behind the latest release	warning	⚠️	expandable section naming the affected release lines, pointing at the Gradle Security Subscription
Out of date — one major behind, or more than two minors behind on the current major	notice	ℹ️	one-line legend pointing at the Gradle release lifecycle docs
Current	none	—	—

Deliberately not reported: patch releases (being on 9.7.0 when 9.7.1 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.

Note that these annotations are emitted independently of the add-job-summary setting: setting add-job-summary: 'never' suppresses the Job Summary itself, but the warning and notice annotations remain.

Gradle itself is now reported in the dependency graph

The dependency-submission action now applies v1.5.0 of the GitHub Dependency Graph Gradle Plugin (up from v1.4.2) (#1069).

The headline change is that the Gradle Build Tool running the build is now reported as an org.gradle:gradle-core dependency, so that GitHub can surface known vulnerabilities in the version of Gradle used to run your build. These are the coordinates that GitHub advisories for the Gradle Build Tool are published against.

Details worth knowing:

• The entry is always reported as a direct dependency with development scope.
• It is not affected by the project, configuration or scope filters, so it appears even in graphs that filter aggressively.

... (truncated)

Commits

• 8da46b5 [bot] Update dist directory
• dcf6f72 Merge commit from fork
• bf74269 Update to latest Dependency Graph plugin (#1106)
• 65a6ba9 [bot] Update dist directory
• 35eba4f Combined dependency updates (#1105)
• 1cff18a Update known wrapper checksums (#1075)
• 399f0d3 Update known wrapper checksums
• ecf8cf2 Bump references to Develocity Gradle plugin from 4.5.1 to 4.6.0 (#1080)
• d740e82 Bump references to Develocity Gradle plugin from 4.5.1 to 4.6.0
• f9f39a9 Bump references to Develocity Gradle plugin from 4.5.0 to 4.5.1 (#1072)
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions