Skip to content

docs: move the unreleased changes under 0.6.5, check the dated claims again, correct the Corretto checksum remarks and note that Foojay has no CRaC builds - #125

Merged
linghengqian merged 2 commits into
mainfrom
docs/refresh-after-0.6.5
Nov 3, 2026
Merged

linghengqian merged 2 commits into
mainfrom
docs/refresh-after-0.6.5

Conversation

@linghengqian

@linghengqian linghengqian commented Nov 3, 2026 •

Copy link
Copy Markdown
Member
  • docs: move the unreleased changes under 0.6.5, check the dated claims again, correct the Corretto checksum remarks and note that Foojay has no CRaC builds.

Documentation only. After the release, as for 0.6.2 to 0.6.4:

  • docs/changes.md and its translation: "Unreleased" becomes 0.6.5 (2026-11-03, the UTC day of the release), and the sentence about main being ahead of the latest release goes.
  • docs/sdkmanrc.md and its translation: the "Unreleased: release 0.6.4 ..." remark about the number after the + in the identifiers of Oracle GraalVM and GraalVM Community goes. changes.md has what it said. grep -rn -i -e unreleased -e 未发布 docs README* now finds only the steps in development.md (and "从未发布过" in zh-CN/e2e.md, which is no remark), no page names 0.6.4 outside changes.md, and no 2026-11-02 is left.

Corrected, found while comparing the quoted data with Foojay:

  • docs/foojay.md, docs/troubleshooting.md, the 0.6.4 entry of docs/changes.md and their translations said that Corretto 8 comes with a checksum file and that only "Corretto after 8" has none (fix: verify downloads against the checksum Foojay lists, so vfox install java@25.0.2-graalce and the like no longer end with WARNING: Checksum is not provided, skip verify... #120). Foojay lists an MD5 file only on a record without a build number (amazon-corretto-8-x64-linux-jdk.tar.gz, java_version 8, and likewise 11 to 25), which the plugin never installs: java@8-amzn installs 8.0.512-amzn, and the numbered releases have no checksum. vfox plugin run . PreInstall gives no checksum for 8-amzn, 8.0.512-amzn, 11-amzn, 17-amzn, 21-amzn, 25-amzn and 27-amzn on Linux x64, and for 8-amzn on Linux arm64, macOS x64 and arm64 and Windows x64 as well. So every Corretto install ends with vfox's warning, and the three pages now say that.

Added:

  • docs/sdkmanrc.md and its translation say that SDKMAN lists CRaC builds of Liberica and Zulu (21.0.13.0-crac+12-librca, 25.0.4.1-crac+1-zulu), that it downloads them from the vendors (github.com/bell-sw/Liberica/...-crac.tar.gz, cdn.azul.com/zulu/bin/...-ca-crac-...), and that the plugin has none to install, so an identifier with crac selects nothing (ParseLegacyFile returns an empty version). Foojay is not a source for them: none of the 35,562 JDK packages of its 31 distributions has crac in a field or a file name, feature=crac changes no answer (the feature of the API is for early-access features of Oracle OpenJDK, see its spec), and foojayio/discoapi has no issue about it. Installing them would need a second source next to Foojay, as for Loongnix (BellSoft's and Azul's APIs); that is not part of this change.

Dated claims run again on 2026-11-03, and their dates are 2026-11-03 now (they were 2026-11-02):

  • docs/native-image.md and its translation, in ubuntu:26.04 containers without a compiler and in fedora:44, with the plugin of this branch (vfox add java --source), vfox install and vfox use --global:
    • GraalVM Community 25.0.2 and 25.4.4.1.1, Oracle GraalVM 25.0.5, Mandrel 25.0.5, Liberica NIK 25.0.4.1 and Gluon GraalVM 22.1.0.1: without the packages native-image stops after 1 to 6 s with Default native-compiler executable 'gcc' not found via environment variable PATH, and zlib1g-dev alone does not change that. gcc, libc6-dev and zlib1g-dev, with no g++ and no make, build a hello world in 22 to 52 s and it runs. build-essential without zlib1g-dev fails when it links, after 29 to 52 s, with Linker command exited with 1, It appears as though libz:.a is missing and cannot find -lz: No such file or directory. With build-essential and zlib1g-dev it builds.
    • 22.3.3-grl11, 21.2-grl16, 22.3.3-grl17 and 22.3.1-grl19: native-image is command not found, gu install native-image works (5 to 10 s), and the build then stops without the packages and builds with them. 21.3.1-grl8: gu install native-image fails with Internal error occurred: A JSONObject text must begin with '{', as https://oca.opensource.oracle.com/gds/meta-data.json answers a web page (content-type: text/html), and gu -L install of native-image-installable-svm-java8-linux-amd64-21.3.1.jar works, after which the packages are needed as well.
    • Fedora 44: gcc, glibc-devel and zlib-devel, without libstdc++-static, build the hello world with GraalVM Community 25.0.2 in 35 s.
    • The "What was checked" paragraph now names all five GraalVM CE releases, where it named 22.3.3-grl17 only.
  • docs/e2e.md and its translation: Foojay lists a checksum for the pinned release of every default distribution on every runner. vfox plugin run . PreInstall for 25.0.2 (OpenJDK), 21.0.8-tem, 25.0.4-librca-fx, 21.0.5-jb and 25.0.2-graalce on Linux and Windows, x64 and arm64, gives a SHA-256 (OpenJDK, Temurin, GraalVM Community), SHA-1 (Liberica) or SHA-512 (JetBrains) digest each time, as the paragraph says. OpenJDK and GraalVM Community have no Windows ARM64 build, which the suite skips.
  • docs/foojay.md, the checksum table and its example: see the Corretto correction above.

Data, compared on 2026-11-03 (queries as in development.md, parsed with Python because the host has no jq):

  • Unchanged: the platform table (31 distributions by 8 platforms, in both languages), the JavaFX table (four distributions, none for Alpine arm64), where Foojay links each distribution to (mirror.md: the newest build of every major and the oldest one, for Linux x64), the checksum table of foojay.md for the newest release of each distribution (apart from Corretto above), the numbers in README.md (11 distributions with Alpine x64, 7 with Alpine arm64, 5 with Windows ARM64), the notes under "Only some releases" for Windows ARM64, Apple silicon, Intel Macs, Alpine, Trava, AdoptOpenJDK's OpenJ9 and OJDKBuild, the examples with output in foojay.md, and the "Other CPUs" lists (32-bit ARM and x86, riscv64, ppc64le, s390x; Foojay still answers HTTP 400 invalid architecture for loong64).
  • Unchanged: Red Hat's downloads. Foojay's packages for Linux arm64 (3), ppc64le (2), Windows x64 (the one zip) and 11.0.15 and 11.0.16 for Linux x64 answer 404 (they point to openjdk-sources.osci.io, which no longer has the files, and vfox ends with source file not found), while 21.0.x for Linux x64 downloads from developers.redhat.com.
  • Unchanged: java@21-tem is 21.0.13+9-tem, java@28.ea-open is 28-ea+21, java@25-graal is 25.0.5.0.3-graal, java@25-graalce is 25.4.4.1.1-graalce (all as vfox plugin run . PreInstall answers), vfox search java all lists 2,646 lines on Linux x64 ("about 2,600"), SDKMAN's default is 25.0.5.0+8-tem, and its list has none of Dragonwell, Trava, AdoptOpenJDK, Gluon GraalVM, GraalVM CE 8 to 19, Eliya, OJDKBuild, OpenLogic, Red Hat and Semeru certified. Eliya's site still says its SDKMAN registration is in progress. vfox 1.0.13 is still the newest vfox.
  • Not repeated: the Loongnix archive (loongnix.md).

The 0.6.5 entry is the plugin's behaviour: with 25.0.5-graal, 25.0.5.0.3-graal and 25.4.4.1.1-graal installed, a .sdkmanrc with java=25.0.5.0+3-graal selects 25.0.5.0.3-graal, and java=25.4.4.1+1-graalce selects 25.4.4.1.1-graalce (vfox plugin run . ParseLegacyFile).

vfox plugin test . passes, and the relative links and anchors of all 33 Markdown files resolve (340 links, a script that follows GitHub's rules for the anchors of headings; it was clean before the change too). The English and Chinese pages have the same headings, tables and code blocks apart from translated comments, as before the change.

… and correct what the docs say about the checksum of Corretto

After the release:
- `docs/changes.md` and its translation: "Unreleased" becomes 0.6.5 (2026-11-03), and the sentence about `main` being ahead of the latest release goes.
- `docs/sdkmanrc.md` and its translation: the "Unreleased: release 0.6.4 ..." remark goes. `changes.md` has what it said.

Corrected, found while comparing the quoted data with Foojay:
- `docs/foojay.md`, `docs/troubleshooting.md`, the 0.6.4 entry of `docs/changes.md` and their translations said that Corretto 8 comes with a checksum file and that only the releases after 8 do not. Foojay lists an MD5 file only on a record without a build number (`8`, and likewise 11 to 25), which the plugin never installs. `java@8-amzn` installs `8.0.512-amzn`, like every other Corretto install, and vfox warns that there is no checksum.
- The checksum table and its example in `docs/foojay.md` were compared again, so their date is 2026-11-03.
…eck of e2e.md again, and say that Foojay has no CRaC builds

- `docs/native-image.md` and its translation: the checks dated 2026-11-02 were run again on 2026-11-03 in Ubuntu 26.04 and Fedora 44 containers, and every statement held. The "What was checked" paragraph now also names the other GraalVM CE releases: `22.3.3-grl11`, `21.2-grl16` and `22.3.1-grl19` after `gu install native-image`, and `21.3.1-grl8` after `gu -L install` of the downloaded file.
- `docs/e2e.md` and its translation: Foojay lists a checksum for the pinned release of every default distribution on every runner, compared again on 2026-11-03 (`open` and `graalce` have no Windows ARM64 build, which the suite skips).
- `docs/sdkmanrc.md` and its translation: SDKMAN lists CRaC builds of Liberica and Zulu (`21.0.13.0-crac+12-librca`), which it downloads from the vendors. None of Foojay's 35,562 JDK packages is a CRaC build, so the plugin has none to install and an identifier with `crac` selects nothing.
@linghengqian linghengqian changed the title docs: move the unreleased changes under 0.6.5, drop the 0.6.4 remarks and correct what the docs say about the checksum of Corretto docs: move the unreleased changes under 0.6.5, check the dated claims again, correct the Corretto checksum remarks and note that Foojay has no CRaC builds Nov 3, 2026
@linghengqian linghengqian added the enhancement New feature or request label Nov 3, 2026
@linghengqian
linghengqian merged commit 2a4e569 into main Nov 3, 2026
11 checks passed
@linghengqian
linghengqian deleted the docs/refresh-after-0.6.5 branch November 3, 2026 09:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant