chore(deps): update github-actions non-major dependencies

[we-renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
gradle/actions	action	minor	v6.3.0 → v6.4.0
mikepenz/action-junit-report	action	minor	v6.5.0 → v6.6.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

gradle/actions

v6.4.0

Compare Source

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.
• Expect dependency graphs to gain this one new entry the first time a build runs after upgrading.

A new Gradle signing key, if you use dependency verification

[!IMPORTANT]
If your build has dependency verification
enabled, you must add a second trusted key before upgrading, or Dependency Graph generation will
fail signature verification.

github-dependency-graph-gradle-plugin 1.5.0 is signed with a new Gradle signing subkey, and the
key previously documented in our setup guide has been revoked upstream:

Artifact	Signing key
org.gradle:github-dependency-graph-gradle-plugin 1.5.0 and later	E2879931BCA1A42E55F2D64DD9B2DFBD9F3298BA (new)
org.gradle plugin versions before the rotation	7B79ADD11F8A779FE90FD3D0893A028475557671 (old, revoked)
com.gradle Develocity Gradle plugin, including 4.5.0	7B79ADD11F8A779FE90FD3D0893A028475557671 (old, revoked)

Because the Develocity Gradle plugin is still signed with the old key, you should trust both keys
rather than swapping one for the other — replacing the old key outright will break Develocity
injection. The documented snippet in
docs/setup-gradle.md
has been updated accordingly (#​1071):

<trusted-keys>
   <trusted-key id="7B79ADD11F8A779FE90FD3D0893A028475557671">
      <trusting group="com.gradle"/>
      <trusting group="org.gradle"/>
   </trusted-key>
   <trusted-key id="E2879931BCA1A42E55F2D64DD9B2DFBD9F3298BA">
      <trusting group="org.gradle"/>
   </trusted-key>
</trusted-keys>

cache-provider: external for externally managed Gradle User Home

Builds that save and restore Gradle User Home by some other mechanism (Develocity Artifact Cache, for
example) previously had to set cache-disabled: true, which was misleading: caching wasn't disabled,
it just wasn't managed by this action, and the Job Summary reported it as "Disabled".

cache-provider: external skips Gradle User Home restore/save exactly as cache-disabled does, but
reports a distinct External status in the Job Summary explaining that caching is handled by
another provider (#​1059).

- uses: gradle/actions/setup-gradle@v6
  with:
    cache-provider: 'external'

Develocity access keys containing OIDC tokens now work

Short-lived-token handling validated the server=key[;server=key]* access key format with a regex
whose key portion was too strict, so an access key holding an OIDC token value was rejected
outright. Worse, had it passed the regex, parsing split each entry on = and kept only the second
field — silently truncating any key containing = (as JWT padding does) and sending the mangled
key to the server. Both problems are fixed (#​1061).

Job Summary attribution

Job summaries produced by setup-gradle and dependency-submission now carry a top-level heading
naming the action, so the block stays attributable when another action's summary content lands in the
same job (#​1058).

Updated defaults

• GitHub Dependency Graph Gradle Plugin: 1.4.2 → 1.5.0
• 5 new known-good wrapper checksums for wrapper-validation (368 → 373 entries)

What's Changed

• Bump the github-actions group across 3 directories with 6 updates by @​dependabot[bot] in #​1039
• Bump the npm-dependencies group in /sources with 3 updates by @​dependabot[bot] in #​1038
• Add action heading to Gradle job summary by @​bigdaz in #​1058
• Add cache-provider: external to skip Gradle User Home caching by @​bigdaz in #​1059
• Relax Develocity access key format validation by @​bigdaz in #​1061
• Use the root-qualified :wrapper task by @​cobexer in #​1064
• Report EOL and maintenance status for Gradle versions by @​ov7a in #​1057
• Update dependencies by @​bigdaz in #​1065
• Update .tool-versions: node 24.18.0, gradle 9.7.1, java 17 by @​bigdaz in #​1068
• Combined automated updates: wrapper checksums, npm dependencies, setup-java by @​bigdaz in #​1070
• Bump dependency-graph-gradle-plugin to 1.5.0 by @​bigdaz in #​1069
• Document the new Gradle signing key for dependency verification by @​bigdaz in #​1071

New Contributors

• @​cobexer made their first contribution in #​1064
• @​ov7a made their first contribution in #​1057

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

mikepenz/action-junit-report

v6.6.1

Compare Source

🔒 Security fix

Upgrade to v6.6.1 if you process JUnit reports from untrusted sources, including fork pull requests.

This release fixes GHSA-448p-3p5j-c948: test and suite names could inject HTML or Markdown into Job Summaries and PR comments, allowing misleading content, links or images to appear in test reports. The issue affects versions through v6.6.0. Its assessed severity is low; the reported impact is content spoofing, not JavaScript execution.

The fix escapes report-derived text in detailed and flaky summaries, grouped suite headings, and check names and links when group_reports: false. It also handles line breaks that could allow Markdown injection.

Thank you to @​f0909172434 for responsibly reporting this vulnerability.

📦 Dependencies

• Update source-map-js to patched version 1.2.2 (#​1632).
• Update mikepenz/release-changelog-builder-action to v6.4.0 (#​1631).

Contributors

@​mikepenz, @​renovate-mike[bot], and security reporter @​f0909172434.

v6.6.0

Compare Source

🚀 Features

• feat: add failed_summary option to list failed tests with logs
  • PR: #​1622

📦 Dependencies

• chore(deps): update dependency fast-uri to v4.1.3 [security]
  • PR: #​1620
• chore(deps): update mikepenz/release-changelog-builder-action action to v6.3.0
  • PR: #​1621
• fix: update vulnerable npm dependencies
  • PR: #​1623
• chore(deps): update node devdependency non-major updates
  • PR: #​1624
• chore(deps): update dependency fast-uri to v4.2.1
  • PR: #​1625
• chore(deps): update dependency undici to v8.11.2
  • PR: #​1626
• chore(deps): modernize tooling and enforce seven-day release age
  • PR: #​1628

Contributors:

• @​renovate-mike[bot], @​mikepenz, @​tchiotludo