mirror of
https://github.com/actions/setup-java.git
synced 2026-07-08 22:31:49 +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>
13 lines
309 B
TypeScript
13 lines
309 B
TypeScript
// Models from https://app.swaggerhub.com/apis/azul/metadata/1.0
|
|
|
|
export interface IZuluVersions {
|
|
package_uuid: string;
|
|
name: string;
|
|
download_url: string;
|
|
java_version: Array<number>;
|
|
distro_version: Array<number>;
|
|
openjdk_build_number: number;
|
|
latest: boolean;
|
|
availability_type: string;
|
|
}
|