Bump gradle/actions from 5 to 6

[dependabot]

Bumps gradle/actions from 5 to 6.

Release notes

Sourced from gradle/actions's releases.

v6.0.0

[!IMPORTANT] The release of gradle/actions@v6 contains important changes to the license terms. More details in this blog post. TL;DR: By upgrading to v6, you accept the Terms of Use for the gradle-actions-caching component.

Summary

• Caching functionality of 'gradle-actions' has been extracted into a separate gradle-actions-caching library, and is no longer open-source. See this blog post for more context.
• Existing, rudimentary, configuration-cache support has been removed, pending a fully functional implementation in gradle-actions-caching.
• Dependencies updated to address security vulnerabilities

[!IMPORTANT]

Licensing notice

The caching functionality in `gradle-actions` has been extracted into `gradle-actions-caching`, a proprietary commercial component that is not covered by the MIT License. The bundled `gradle-actions-caching` component is licensed and governed by a separate license, available at https://gradle.com/legal/terms-of-use/.

The `gradle-actions-caching` component is used only when caching is enabled and is not loaded or used when caching is disabled.

Use of the `gradle-actions-caching` component is subject to a separate license, available at https://gradle.com/legal/terms-of-use/. If you do not agree to these license terms, do not use the `gradle-actions-caching` component.

What's Changed

• Bump the npm-dependencies group in /sources with 2 updates by @​dependabot[bot] in gradle/actions#866
• Update known wrapper checksums by @​github-actions[bot] in gradle/actions#868
• Dependency updates by @​bigdaz in gradle/actions#876
• Update known wrapper checksums by @​github-actions[bot] in gradle/actions#878
• Bump @​types/node from 25.3.3 to 25.3.5 in /sources in the npm-dependencies group across 1 directory by @​dependabot[bot] in gradle/actions#877
• Bump the github-actions group across 3 directories with 3 updates by @​dependabot[bot] in gradle/actions#867
• Update known wrapper checksums by @​github-actions[bot] in gradle/actions#881
• Bump the npm-dependencies group in /sources with 6 updates by @​dependabot[bot] in gradle/actions#879
• Bump the github-actions group across 3 directories with 5 updates by @​dependabot[bot] in gradle/actions#880
• Remove configuration-cache support by @​bigdaz in gradle/actions#884
• Extract caching logic into a separate gradle-actions-caching component by @​bigdaz in gradle/actions#885
• Update gradle-actions-caching library to v0.3.0 by @​bot-githubaction in gradle/actions#899
• Avoid windows shutdown bug by @​bigdaz in gradle/actions#900
• Dependency updates by @​bigdaz in gradle/actions#905
• Fix critical and high npm vulnerabilities by @​bigdaz in gradle/actions#904
• Fix rendering of job-disabled message by @​bigdaz in gradle/actions#909

Full Changelog: gradle/actions@v5.0.2...v6.0.0

v5.0.2

Summary

This release contains no functional changes. It updates dependencies and known Gradle wrapper checksums.

What's Changed

• Update dependencies by @​bigdaz in gradle/actions#851

... (truncated)

Commits

• 50e97c2 Link to docs for caching providers
• f2e6298 Restructure caching documentation for basic and enhanced providers (#934)
• b294b1e Really fix integ-test-full
• 83d3189 Revise license details for gradle-actions-caching
• 1d5db06 Update license link for gradle-actions-caching component
• 1c80961 Fix license link for Enhanced Caching component
• 9e99920 Fix integ-test-full workflow
• bb8aaaf Fix workflow permissions
• f5dfb43 [bot] Update dist directory
• ff9ae24 Add open-source 'basic' cache provider and revamp licensing documentation (#930)
• Additional commits viewable in compare view

[PattaFeuFeu]

@bocops How do you feel about the licence change introduced with the version bump? Given that this is an open-source project, I’m cautiously willing to agree and update to 6.

[bocops]

@PattaFeuFeu Considering that we're using MIT license for this project, there isn't much that people can't already do with our code. ;) Insofar, I agree. However, there's an update to the blog post linked from the release notes summary, which seems to offer another option: https://blog.gradle.org/choice-clarity-future-caching-gradle-actions.

I don't know completely what the difference between the proprietary "enhanced caching" mechanism in 6.0.0 and the "basic" cache provider in 6.1.0 really is, and if we can use the latter - but if we can, we might want to skip 6.0.0 and update to 6.1.0 with that "basic" configuration in place directly, just to be on the safe side.