This message was deleted.

I don't know a reason but there is an open issue: https://github.com/gradle/gradle/issues/22882

given that the ecosystem (dependencies in general, not just Gradle) predates the semver document, IMO you should use something that handles all of https://maven.apache.org/pom.html#version-order-specification / https://docs.gradle.org/current/userguide/single_versions.html#version_ordering and not just versions that match semver

sure, there’s lots of different version schemes in the world. some better than others. though, i don’t see a benefit to continuing to use a less-than-ideal approach where the version format changes across releases. (

7.2

->

7.2.1

->

7.3

).

I wouldn't mind Gradle versioning becoming more like semver, given that the feature release process pretty much follows it anyway. my point is that you need to handle general Maven versions regardless of Gradle's versioning scheme

well not in my script that's validating a minimum gradle version :)

I had to add a

.0

to the Docker Library images because otherwise the tag of the first minor release would be overwritten, but all the other patch releases wouldn't have their tags overwritten, which is confusing.