This repository has been archived on 2026-08-26. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
f4bfb3ddea Report concrete versions for floating Oracle JDK downloads (#1213)
* Fix floating Oracle JDK version resolution

Co-authored-by: Copilot App <[email protected]>

* Update generated distribution bundles

Co-authored-by: Copilot App <[email protected]>

* Harden floating artifact cache identity

Co-authored-by: Copilot App <[email protected]>

* Regenerate setup bundle after cache hardening

Co-authored-by: Copilot App <[email protected]>

* Temporarily enable hosted full validation

Co-authored-by: Copilot App <[email protected]>

* Export hosted formatting results

Co-authored-by: Copilot App <[email protected]>

* Apply repository formatting

Co-authored-by: Copilot App <[email protected]>

* Run hosted validation after formatting

Co-authored-by: Copilot App <[email protected]>

* Correct floating version regression tests

Co-authored-by: Copilot App <[email protected]>

* Remove temporary validation wiring

Co-authored-by: Copilot App <[email protected]>

* Cache checksum-less floating artifacts by their response fingerprint

Oracle and Oracle GraalVM do not always publish a `.sha256` sibling next
to a `/latest/` artifact. Those floating releases were excluded from both
the resolution cache and the JDK cache, so `cache-jdk` users lost caching
entirely for them.

A floating URL is a constant string, so it cannot serve as a cache
identity on its own — a stale entry would be reused forever. Instead,
derive a validator from the headers of the HEAD request that already
resolves the artifact: the ETag when present, otherwise `Last-Modified`
combined with `Content-Length`. Republishing changes the validator, which
changes the cache key, so a new build is downloaded rather than masked.

`getJdkReleaseIdentity` now falls back to that fingerprint before the
URL, and the floating cache gates ask whether the release has a stable
identity (checksum or fingerprint) rather than a checksum specifically. A
floating release with neither is still left uncached.

Co-authored-by: Copilot App <[email protected]>

---------

Co-authored-by: Copilot App <[email protected]>
Co-authored-by: Bruno Borges <[email protected]>
2026-08-05 11:57:27 -04:00
..
2022-12-26 09:43:06 +01:00
2025-01-21 16:15:18 -06:00