mirror of
https://github.com/actions/setup-java.git
synced 2026-07-08 14:21:50 +00:00
12c069fb55
The Azul Metadata API returns java_version as a 3-element array (e.g. [17,0,7]) and reports the build number separately in openjdk_build_number. The migration mapped version directly from java_version, dropping the build and breaking exact-version lookups like 17.0.7+7 (e2e failure: "No matching version found for SemVer"). Add openjdk_build_number to IZuluVersions and append it to java_version before converting to semver so resolved versions retain the build (e.g. 17.0.7+7). Update the zulu test fixtures to mirror the real API shape (3-element java_version plus openjdk_build_number) so unit tests exercise the actual response format, and rebuild dist. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| adopt.json | ||
| corretto.json | ||
| dragonwell.json | ||
| jetbrains.json | ||
| liberica-linux.json | ||
| liberica-windows.json | ||
| liberica.json | ||
| microsoft.json | ||
| sapmachine.json | ||
| sdkman-java-versions.csv | ||
| semeru.json | ||
| temurin.json | ||
| zulu-linux.json | ||
| zulu-releases-default.json | ||
| zulu-windows.json | ||