For some reason, Oracle labels the initial release of a major JDK version, as e.g. 25, followed by 25.0.1, 25.0.2...
This is what happened for JDK 24, JDK 23, JDK 22, etc.
I googled a bit but could find a reason why the initial release is not e.g. 25.0.0.
This may seem a trivial issue, but it's actually causing some issues with tools (like Renovate Bot) which look for a specific pattern in versions.
For example, I currently reference version eclipse-temurin:21.0.8_9-jdk@sha256:03e5fbb9980a03e4b3d11676082650a4443108aaf1f7b7d9cc338171c5a90070 in my Dockerfile, GitLab CI files, etc.
At the moment, I can only replace it with eclipse-temurin:25_36-jdk@sha256:..., which is confusing as it appears as if that the change introduced a lost of "version precision".
I see that some vendors did release a Docker image for JDK 25 as 25.0.0:
Some did not:
Could you consider doing like Azul and Amazon, and provide JDK 25+36 as a Docker image with tag 25.0.0_36?
For some reason, Oracle labels the initial release of a major JDK version, as e.g.
25, followed by25.0.1,25.0.2...This is what happened for JDK 24, JDK 23, JDK 22, etc.
I googled a bit but could find a reason why the initial release is not e.g.
25.0.0.This may seem a trivial issue, but it's actually causing some issues with tools (like Renovate Bot) which look for a specific pattern in versions.
For example, I currently reference version
eclipse-temurin:21.0.8_9-jdk@sha256:03e5fbb9980a03e4b3d11676082650a4443108aaf1f7b7d9cc338171c5a90070in my Dockerfile, GitLab CI files, etc.At the moment, I can only replace it with
eclipse-temurin:25_36-jdk@sha256:..., which is confusing as it appears as if that the change introduced a lost of "version precision".I see that some vendors did release a Docker image for JDK 25 as
25.0.0:Some did not:
Could you consider doing like Azul and Amazon, and provide JDK 25+36 as a Docker image with tag
25.0.0_36?