Update data

[github-actions]

Automated changes by create-pull-request GitHub action

[greptile-apps]

Greptile Summary

This automated PR reorders existing EA JDK entries within the four platform JSON files. No new versions, checksums, or download URLs were added or removed — all data values are identical to the previous commit.

• The entries for JDK 25–28 were repositioned within each array, but the resulting order is non-sequential in three of the four files (aarch64 ends 27→28→25→26; linux/x86_64 ends 26→25→27→28; windows/x86_64 ends 25→26→28→27). macosx/x86_64 is the only file where the reordering produces a reasonable result.
• The macosx/x86_64 change moves the JDK 27 entry after JDK 25, keeping per-entry data intact.

Confidence Score: 4/5

Safe to merge if consumers do not rely on the array being version-sorted; no data was changed, only entry positions.

All four files contain the exact same checksums, URLs, and version strings as before — no data was altered. The only observable change is that the last few EA entries appear in a different order within each array. Three files end in a non-sequential version order, which could trip a consumer that picks the latest EA release by position rather than by inspecting java_version. This is worth a second look on the generation script but is not a data integrity issue.

public/api/jvm/ea/linux/aarch64.json, public/api/jvm/ea/linux/x86_64.json, and public/api/jvm/ea/windows/x86_64.json — their trailing EA entries are not in version-ascending order.

Important Files Changed

Filename	Overview
public/api/jvm/ea/linux/aarch64.json	Reorders the last 4 EA entries (JDK 25–28) from version-ascending order (25→26→27→28) to 27→28→25→26 — same data, non-sequential result order
public/api/jvm/ea/linux/x86_64.json	Reorders the last 4 EA entries; JDK 28 moves from first to last position, leaving order 26→25→27→28 — data unchanged, sort order inconsistent
public/api/jvm/ea/macosx/x86_64.json	JDK 27 entry moved from before JDK 26 to after JDK 25; same data, position change only
public/api/jvm/ea/windows/x86_64.json	Reorders last 4 EA entries from 26→27→28→25 to 25→26→28→27 — JDK 28 still appears before JDK 27, data unchanged

_{Reviews (1): Last reviewed commit: "Update data" | Re-trigger Greptile}

[greptile-apps]

Inconsistent sort order after reordering

No new data was added or removed across any of the four changed files — the only change is that existing EA entries were repositioned within each array. The resulting order is non-sequential across all files: aarch64 ends in 27→28→25→26, linux/x86_64 ends in 26→25→27→28, and windows/x86_64 ends in 25→26→28→27. If any consumer locates the latest EA release by reading the last array element, it will now receive the wrong version. It would be worth verifying that the data-generation script's sort logic is behaving as intended.