Update data

[github-actions]

Automated changes by create-pull-request GitHub action

[greptile-apps]

Greptile Summary

This automated refresh adds Temurin 26.0.2.1 and Dragonwell 17.0.20/21.0.12 artifacts across five GA platform catalogs.

• Adds Temurin JDK and JRE artifacts for Alpine Linux on AArch64.
• Adds Dragonwell standard and extended JDK artifacts for Alpine Linux, Linux, and Windows.
• Several new Dragonwell records do not conform to the published checksum schema.

Confidence Score: 4/5

The PR should not merge until the new Dragonwell records conform to the published checksum contract or the API schema is explicitly updated to permit missing checksums.

The generated catalogs publish newly added records with null checksums even though the public OpenAPI schema requires every checksum to be a digest-formatted string, so schema-validating consumers can reject the refreshed data.

Files Needing Attention: public/api/jvm/ga/alpine-linux/x86_64.json, public/api/jvm/ga/linux/aarch64.json, public/api/jvm/ga/linux/x86_64.json, public/api/jvm/ga/windows/x86_64.json

Important Files Changed

Filename	Overview
public/api/jvm/ga/alpine-linux/aarch64.json	Adds checksummed Temurin 26.0.2.1 JDK and JRE records with the expected musl platform feature.
public/api/jvm/ga/alpine-linux/x86_64.json	Adds Dragonwell releases whose null checksums violate the required public API record schema.
public/api/jvm/ga/linux/aarch64.json	Adds Temurin and Dragonwell artifacts, with each new Dragonwell record carrying a schema-invalid null checksum.
public/api/jvm/ga/linux/x86_64.json	Adds musl and standard Dragonwell variants for two releases, all with schema-invalid null checksums.
public/api/jvm/ga/windows/x86_64.json	Adds three Dragonwell JDK records whose null checksums violate the published response contract.

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

[greptile-apps]

Null checksums violate API contract

When a schema-validating consumer reads this new Dragonwell record, checksum: null violates the required digest-formatted string in the jvm_data schema, causing the record or containing catalog response to be rejected. The same invalid value is introduced for the new Dragonwell releases in the Linux and Windows catalogs.

Knowledge Base Used:

• Published catalog API
• Catalog release publication