Renaming coordinates without a newVersion carries the old version over to the new artifact

What version of OpenRewrite are you using?

Latest main (reproduced at 560b40cc63).

What is the smallest, simplest way to reproduce the problem?

ChangeDependencyGroupIdAndArtifactId / ChangeManagedDependencyGroupIdAndArtifactId without a newVersion renames the coordinates of a <dependencyManagement> entry but keeps the version that belonged to the old coordinates:

rewriteRun(
  spec -> spec.recipe(new ChangeDependencyGroupIdAndArtifactId(
    "javax.servlet", "javax.servlet-api", "jakarta.servlet", "jakarta.servlet-api", null, null)),
  pomXml(
    """
      <project>
          <groupId>com.mycompany.app</groupId>
          <artifactId>my-app</artifactId>
          <version>1</version>
          <dependencyManagement>
              <dependencies>
                  <dependency>
                      <groupId>javax.servlet</groupId>
                      <artifactId>javax.servlet-api</artifactId>
                      <version>4.0.1</version>
                  </dependency>
              </dependencies>
          </dependencyManagement>
          <dependencies>
              <dependency>
                  <groupId>javax.servlet</groupId>
                  <artifactId>javax.servlet-api</artifactId>
              </dependency>
          </dependencies>
      </project>
      """
  )
);

What did you expect to see?

Either a version that exists for the new coordinates, or no change.

What did you see instead?

jakarta.servlet:jakarta.servlet-api:4.0.1, which does not exist:

<!--~~(jakarta.servlet:jakarta.servlet-api:4.0.1 failed. Unable to download POM: jakarta.servlet:jakarta.servlet-api:4.0.1. Tried repositories:
https://repo.maven.apache.org/maven2: HTTP 404)~~>-->

• Version lines rarely carry over across a groupId change (javax.* → jakarta.* is the common case), so carrying the old version over is usually wrong. Same applies to a <dependency> with an explicit <version>. Related to #8462, which covers the case where the version is dropped entirely rather than carried over.

Are you interested in contributing a fix?

Not immediately.

Start with the ChangeDependencyGroupIdAndArtifactId and ChangeManagedDependencyGroupIdAndArtifactId recipe entry points and reproduce the dependencyManagement example from the issue. Check the existing recipe tests around coordinate and version changes, then verify that renaming without newVersion does not carry an invalid old version into the new coordinates, including for an explicit dependency version.