Upgrade transitive Gradle dependencies
Apache 2.0Upgrades the version of a transitive dependency in a Gradle build file. There are many ways to do this in Gradle, so the mechanism for upgrading a transitive dependency must be considered carefully depending on your style of dependency management.
org. openrewrite. gradle. UpgradeTransitiveDependencyVersionRequired
The first part of a dependency coordinate com.google.guava:guava:VERSION. This can be a glob expression.
The second part of a dependency coordinate com.google.guava:guava:VERSION. This can be a glob expression.
Optional
An exact version number or node-style semver selector used to select the version number. You can also use latest.release for the latest available version and latest.patch if the current version is a valid semantic version. For more details, you can look at the documentation page of version selectors. Defaults to latest.release.
Allows version selection to be extended beyond the original Node Semver semantics. So for example,Setting 'newVersion' to "25-29" can be paired with a metadata pattern of "-jre" to select Guava 29.0-jre
The reason for upgrading the transitive dependency. For example, we could be responding to a vulnerability.
A list of configurations to consider during the upgrade. For example, For example using implementation, runtimeOnly, we could be responding to a deployable asset vulnerability only (ignoring test scoped vulnerabilities). Separate values with commas.
mod run . --recipe= org. openrewrite. gradle. UpgradeTransitiveDependencyVersion \
-P groupId= 'com. fasterxml. jackson*' \
-P artifactId= 'jackson-module*'Install it once from Recipe actions, then run it on every repository under the current directory. New to the Moderne CLI? Set it up.