ChangeDependency - transitive dependency pitfall

I've observed this in a few spots, recently in the Jackson recipes. But I think it's a pattern problem, so I'm opening it here in rewrite.

Consider a recipe like this, where a library has done a GAV change, and so we have a bunch of ChangeDependency and ChangeType calls to migrate:
https://github.com/openrewrite/rewrite-jackson/blob/b5ff3f25509117b15492d234c9eb7e08dbd5ab66/src/main/resources/META-INF/rewrite/jackson-2-3.yml

ChangeType updates the code to match the library's new version, and ChangeDependency ensures that the project's build picks up the new version instead of the old. All good, all intuitive.

But, it falls down on projects which are pulling in that library transitively, not directly. In that case, the project build will still pull in the library's old version, and the updated project code (referencing the new packages) will not compile.
(unless we're talking about, say, spring-boot-starter-jackson, and some other spring recipe in the chain will handle updating the spring dependency in a way that gets us to the newer jackson)

One way to fix is with a corresponding AddDependency recipe invocation for each ChangeDependency, with acceptTransitive set to true. That's what PRs like this have done (several times even within the same file!):

• https://github.com/openrewrite/rewrite-migrate-java/pull/767
• https://github.com/openrewrite/rewrite-migrate-java/pull/723
• https://github.com/openrewrite/rewrite-migrate-java/pull/835
• https://github.com/openrewrite/rewrite-migrate-java/pull/456

I think this troubleshooting loop could be short-circuited with some new recipe option or composite recipe, which combines the ChangeDependency and AddDependency behaviors.

Thoughts?

Start by reading the ChangeDependency and AddDependency recipe implementations in rewrite, then inspect the referenced jackson-2-3.yml recipe and the linked rewrite-migrate-java pull requests. Determine how transitive dependencies are handled and define a recipe option or composite behavior that avoids repeated AddDependency calls while preserving direct dependency changes.