$ curl -sS https://repo1.maven.org/maven2/org/testcontainers/junit-jupiter/maven-metadata.xml
org.testcontainers
junit-jupiter
1.21.4
1.21.4
... (1.10.0 through 1.21.4, 56 releases total) ...
1.21.4
20251216004330
$ curl -sS https://repo1.maven.org/maven2/org/testcontainers/testcontainers-junit-jupiter/maven-metadata.xml
org.testcontainers
testcontainers-junit-jupiter
2.0.5
2.0.5
2.0.0
2.0.1
2.0.2
2.0.3
2.0.4
2.0.5
20260420182027
# The old artifactId's release history simply stops at 1.21.4 - no 2.x version was ever
# published under org.testcontainers:junit-jupiter. The new artifactId's history starts fresh
# at 2.0.0. This is the real, permanent fork point on Maven Central: "upgrade the version
# number" on your existing junit-jupiter dependency has no 2.x version
# to resolve to - it will stay on 1.21.4 forever, or fail outright for a module whose own
# artifactId was retired rather than just renamed (see 05-legacy-pom-fails-to-resolve-under-2.0.5.txt,
# where this happens to org.testcontainers:postgresql).
#
# This is one rename out of 61: OpenRewrite's own migration recipe documents the full list at
# https://docs.openrewrite.org/recipes/java/testing/testcontainers/testcontainers2dependencies -
# every org.testcontainers: artifact gets a testcontainers- artifactId, same
# groupId, same Maven Central repository. The core artifact, plain org.testcontainers:testcontainers,
# is the one name on the list that did NOT change.