JDK 27 went GA on 15 September 2026 (https://jdk.java.net/27/ now shows "OpenJDK JDK 27 GA Release Builds", build 35), but the API still reports the Oracle OpenJDK 27 package as early access.
What I see
GET /disco/v3.0/packages?distribution=oracle_open_jdk&version=27&latest=available&operating_system=linux&architecture=x64&archive_type=tar.gz&package_type=jdk&release_status=ga returns an empty result.
The same query with release_status=ea returns one package, java_version 27-ea+35, release_status ea. Its direct_download_uri already points at the GA location:
https://download.java.net/java/GA/jdk27/55ce5470a6294008af0057ff4626d0e5/35/GPL/openjdk-27_linux-x64_bin.tar.gz
Meanwhile /disco/v3.0/major_versions lists 27 as ga, and the other distributions (Zulu, Liberica, Corretto, SapMachine, Oracle) already return 27 GA packages. Only oracle_open_jdk is behind.
Expected
The 27 build 35 package labelled 27+35 with release_status ga, like 26+35 and 25+36 are today.
Probable cause
Oracle hosted build 35 under the GA path while the page was still marked "Release-Candidate", so the package was first seen as EA. Since the filename and download URL did not change when the page switched to GA, the hourly update skips it as already known and the stored release status never gets re-evaluated. A forced refresh of the distribution should fix it.
Clients that resolve oracle_open_jdk with the default GA filter (for example the Gradle foojay toolchain resolver) currently cannot find JDK 27 at all. Thanks for looking into it!
JDK 27 went GA on 15 September 2026 (https://jdk.java.net/27/ now shows "OpenJDK JDK 27 GA Release Builds", build 35), but the API still reports the Oracle OpenJDK 27 package as early access.
What I see
GET /disco/v3.0/packages?distribution=oracle_open_jdk&version=27&latest=available&operating_system=linux&architecture=x64&archive_type=tar.gz&package_type=jdk&release_status=gareturns an empty result.The same query with
release_status=eareturns one package,java_version27-ea+35,release_statusea. Itsdirect_download_urialready points at the GA location:Meanwhile
/disco/v3.0/major_versionslists 27 asga, and the other distributions (Zulu, Liberica, Corretto, SapMachine, Oracle) already return 27 GA packages. Onlyoracle_open_jdkis behind.Expected
The 27 build 35 package labelled
27+35withrelease_statusga, like26+35and25+36are today.Probable cause
Oracle hosted build 35 under the GA path while the page was still marked "Release-Candidate", so the package was first seen as EA. Since the filename and download URL did not change when the page switched to GA, the hourly update skips it as already known and the stored release status never gets re-evaluated. A forced refresh of the distribution should fix it.
Clients that resolve
oracle_open_jdkwith the default GA filter (for example the Gradle foojay toolchain resolver) currently cannot find JDK 27 at all. Thanks for looking into it!