mirror of
https://github.com/actions/setup-java.git
synced 2026-08-25 16:00:54 +00:00
f4bfb3ddea
* Fix floating Oracle JDK version resolution Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Update generated distribution bundles Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Harden floating artifact cache identity Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Regenerate setup bundle after cache hardening Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Temporarily enable hosted full validation Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Export hosted formatting results Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Apply repository formatting Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Run hosted validation after formatting Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Correct floating version regression tests Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Remove temporary validation wiring Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * 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 <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Co-authored-by: Bruno Borges <brborges@microsoft.com> |
||
|---|---|---|
| .. | ||
| base-installer.test.ts | ||
| corretto-installer.test.ts | ||
| distribution-factory.lazy-loading.test.ts | ||
| distribution-factory.test.ts | ||
| dragonwell-installer.test.ts | ||
| graalvm-installer.test.ts | ||
| jetbrains-installer.test.ts | ||
| kona-installer.test.ts | ||
| liberica-installer.test.ts | ||
| liberica-linux-installer.test.ts | ||
| liberica-nik-installer.test.ts | ||
| liberica-windows-installer.test.ts | ||
| local-installer.test.ts | ||
| microsoft-installer.test.ts | ||
| openjdk-installer.test.ts | ||
| oracle-installer.test.ts | ||
| sapmachine-installer.test.ts | ||
| semeru-installer.test.ts | ||
| temurin-installer.test.ts | ||
| zulu-installer.test.ts | ||
| zulu-linux-installer.test.ts | ||
| zulu-windows-installer.test.ts | ||