Life is too short to google for dependencies and versions
AndroidX.wear.tiles.material
dependency notation that was pointing to wrong coordinates because of a typo.
The test that was designed to catch this has been fixed to prevent future recurrence.Thanks to @yacine-ser for raising this memory leak issue along with a hint on the culprit, it was very helpful in reproducing and fixing the leak.
refreshVersions
task twice in a row with configuration cache enabled, the second run would fail, even in warning mode. It's now fixed.GcsClient
, and we're very happy with that because it also has the benefit of reducing the total size of refreshVersions when we include its dependencies. Note that this is using internal Gradle APIs, but we've seen that they didn't change in 5 years, and the code path is executed only if you have gcs backed repositories in your project.Thanks to @mgray88 for the contribution in adding ReactiveX, RxBinding, and RxRelay dependency notations!
refreshVersions
task itself is not compatible with configuration cache because it's impossible with the current Gradle APIs.
refreshVersions
task will no longer fail if there's a problem getting versions from a repository. Now, it will add contextual comments in the versions.properties
file, so you know what failed, and don't get fully blocked next time jcenter or another repository undergoes an outage. This should also help if you're running the refreshVersions
task through an unstable internet connection and some network calls fail because of that.Thanks to @imashnake0 for the contribution in adding dependency notations!
Dispatchers.shutdown()
). We believe it caused memory leaks in the Gradle Daemon, and this change, made possible since kotlinx.coroutines 1.6.0 should fix the last memory leak cause.androidx.test
family started diverging, so we changed replaced the version.androidx.test
version key with more specific ones. The migration will be done automatically on upgrade of refreshVersions, without upgrading the versions of androidx.tests
dependencies themselves.We also removed many obsolete dependency notations from refreshVersions. Just like for the 0.30.0 release, this should not break your build as we implemented a robust replacement mechanism that also inserts migration guidance comments. ✨
Thanks to @brady-aiello, @mgray88, and @imashnake0 for their contributions in adding dependency notations!
We raised the minimum supported Gradle version to 6.8, because we started to use Kotlin 1.4 features, and Gradle pins the stdlib version. Since at the time of writing, the latest Gradle version is 7.3, we believe it won't actually block any of our users. We have a short section about updating Gradle on our website here, feel free to check it out if it can help you.
dependencyResolutionManagement
are now supported (Gradle 7+)Since Gradle 7, you can declare repositories of the entire Gradle project (including all subprojects and their buildscript)
in the dependencyResolutionManagement
block in the settings.gradle[.kts]
file.
Unfortunately, refreshVersions didn't support it, so, unless you also kept repositories declared with allprojects
, or per project, you would end up with all version entries in the versions.properties
file marked as unused after running the refreshVersions
task, and you'd not see the newer updates.
This release resolves this issue, and we are eager to use it in our projects ourselves.
Sometimes, libraries get deprecated, or the maintainers change the maven coordinates.
When it happens, this fact is unfortunately not included in the maven-metadata.xml
files, or any other standard metadata. That means tools like refreshVersions will believe you're on the latest versions, when you're not, because it lacks the necessary information.
One example is Google that changed the maven coordinates of all their AndroidX Wear Watchface artifacts several weeks ago.
It took us time to catch-up with this change because we wanted to design a generic mechanism for this recurrent problem, and provide the best experience for you, and ourselves.
From now on, we have the ability to remove old or deprecated built-in dependency notations in refreshVersions, and doing so will not break your builds, nor will it change the dependencies of your project. However, it'll help you notice the deprecation, and it'll help you switch to the replacement dependencies, if any.
The way it works is that we keep a versioned list of all the removals, and on refreshVersions upgrade, an automatic replacement will put back the hardcoded maven coordinates, using the version placeholder, and it will add our hand-written TODO/FIXME comments, along with a perfectly aligned replacement suggestion if there is any, so that moving to the newer artifact is as easy as upgrading to a newer version in the versions.properties
file. We designed the system so that it cannot break your build, even if you were using withVersion(…)
or other DependencyNotation
extensions, even if you have code comments or special string literals.
It also supports the case where we just move a dependency notation to another place, or change its name, without changing the maven coordinates.
Because of this change, it's important that you check the git diff after upgrading refreshVersions and running the first Gradle reload/sync/build, so you can see if there's been any changes, and if you might want to switch to any replacement dependencies.
This change will enable us to keep the built-in dependency notations updated with less effort, so we're very happy to have it ready, and fully tested.
We've already started to take advantage of it to clean up all the discontinued artifacts we found in AndroidX.
dependencyResolutionManagement
block were ignored. Now, they are taken into account.refreshVersionsMigrate
task wasn't inserting new entries in alphabetical order. Now it is.refreshVersionsMigrate
task wasn't migrating buildscript dependencies. Now it is.Thanks to Emil Kantis for the kotest dependencies fixes! Thanks to Kamalesh for the help in updating AndroidX dependency notations! Thanks to Simon Marquis for adding Square.moshi.adapters, and helping contributors using Windows!
Fix a regression that brought a KotlinNullPointerException
in the build. We apologize for the issue. Thanks to Marcin and Craig for the report.
Thanks to Filip Czaplicki, who contributed to the new dependency notations!
We now support npm dependencies for Kotlin/JS!
Just put the version placeholder (_
) in place of the version, and you're good to go.
The version keys follow a simple naming scheme where their id is prefixed with npm
, here are two examples:
version.npm.react=17.0.2
version.npm.@googlemaps/js-api-loader=1.12.2
Special thanks to NikkyAI who authored the feature, and pair-programmed with us to refine it!
Before this release, when we added new dependency notations and shorter version keys, it could lead to an unwanted upgrade of the dependency in the project upgrading refreshVersions. With this release, we make sure to copy the same version if we add or change the version key, and it will also work if we decide to remove one. This ensures that upgrading refreshVersions will not be able to affect your application or library.
Thanks to Brady Aiello from Touchlab for helping out via pair-programming!
Thanks to Brady Aiello again, who contributed to these new dependency notations!
We are now ready to accept dependency notation contributions for high-quality and popular dependencies from the Kotlin ecosystem!
Look for issues with the Dependency notations
and up-for-grabs
tags to find one you can directly contribute to, or submit a new issue to ask for a new one to be added. We updated the contributing guide on the website, it now has a guide dedicated to it here.
## unused
comments on top of unused entries in the versions.properties
file after you run the refreshVersions
task, so you know which ones are obsolete and can be removed.rejectVersionsIf { … }
predicate available in the refreshVersions { … }
extension in your settings.gradle[.kts]
file will allow you to filter any kind of versions you don't want to know about. It can be handy to filter snapshots out for example.withVersionPlaceholder()
, withVersion(…)
, and withoutVersion()
.The refreshVersionsMigrate
will now use the built-in dependency notations if they match existing dependencies.