Heads up - don't just do the major version bump to 6.0.0 for the 'setup-gradle' GitHub action, without being clear about the implications for your setup.

😥

"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."

https://github.com/gradle/actions/releases/tag/v6.0.0

https://github.com/gradle/actions/pull/885

#Gradle #GitHub #Java

GitHub

Release v6.0.0 · gradle/actions

ImportantThe 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-acti...

Jendrik Johannes @jendrik@mastodon.social

· 6mo ago

Replying to

@bigdaz@mastodon.social thanks for sharing and for the addition update. I think it's very good to have that option to explicitly accept the terms without always seeing the notice. Another feedback: adding the following sentence from the post to the release notes of 6.0.0 / 6.0.1 would clarify things quite a bit: "By upgrading to v6, you accept the Terms of Use for the gradle-actions-caching component." (Unless it is already there and I just missed it.)

Jendrik Johannes @jendrik@mastodon.social

· 6mo ago

Replying to

@themrmilchmann@mastodon.social I don't get yet how this works. If you use default config, you get a noisy license info each time the actions runs at run AND post run. If you turn off caching, well you have less caching, but you also have custom config code every time you configure the action. I haven't found how to "accept" the license to turn off the noisy info. I hope there is an option for that. But no matter what you choose, somewhere there is more noise now than before. The product is worse. 🤷‍♀️