Repository navigation
Add jdk-27 (Eclipse Temurin 27, current feature release) - #898
Merged
Merged
Conversation
Temurin 27 GA (jdk-27+35, 2026-09-21), the current Java feature release, as its own package alongside `jdk`. Same shape as jdk-25 in #897. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
/build |
Contributor
|
Warning Review limit reached
This review includes 2 billable files and costs up to $0.50.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 24 minutes for your next included review. View limit details
Comment |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
/build |
bryan-minimal
added a commit
that referenced
this pull request
Oct 16, 2026
All three Java stacks now name jdk-25 (pkgs#897) rather than the `jdk` meta, so a project's Java doesn't move when `jdk` rolls to the next LTS. The header's `$JAVA_HOME/bin/jdb` is plain `jdb` now that #897/#898 link every JDK tool into /usr/bin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jtnkminimal
approved these changes
Oct 16, 2026
This was referenced Oct 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
packages/jdk-27: Eclipse Temurin 27 GA (jdk-27+35, published 2026-09-21), the current Java feature release (non-LTS). It is a separate package, sojdkstays put. The shape is copied exactly frompackages/jdk-25in #897 (same outputs, runtime deps and tests) with every 25-specific value changed. The branch is cut frommainbecause jdk-27 does not depend on #897.Sources (from
adoptium/temurin27-binaries, releasejdk-27+35).sha256.txt)OpenJDK27U-jdk_x64_linux_hotspot_27_35.tar.gz1cf69a4848ffb728b3b260dfd45206a51566ab571a02a30092271d4c580bccbcOpenJDK27U-jdk_aarch64_linux_hotspot_27_35.tar.gze4ec5c7276290c7bde0baecba9a29be4962f5388684296406a9799d465936087I re-hashed the x64 tarball locally and it matches. Its top directory is
jdk-27+35/, andreleasesaysJAVA_VERSION="27",JAVA_RUNTIME_VERSION="27+35". The top-level layout (bin conf include legal lib man NOTICE release, with nojmods/) is the same one the jdk-25 outputs already cover.The GA release has no dotted version
A GA release is
27, not27.0.0. Soversion = "27"andbuild_num = "35", and the unchanged URL template andbuild.sh(OpenJDK27U-jdk_${PLATFORM}_linux_hotspot_${VERSION}_${BUILD_NUM}.tar.gz,cd "jdk-${VERSION}+${BUILD_NUM}") produce the exact asset names and directory. I checked this withmip dump --packages: the evaluated amd64 URL is.../download/jdk-27+35/OpenJDK27U-jdk_x64_linux_hotspot_27_35.tar.gz.java_versiongrepsversion "27.Version checking: this package is not pinned yet
jdk-X+N, and sc#502 strips the+buildmetadata, sojdk-27+35is read as27. The first update (jdk-27.0.1+N) is read as27.0.1, and the updater rewrites bothversionandbuild_num. That update also moves the shape from undotted to dotted, which is worth checking on the first auto-update PR.jdk-27tracks the current feature release line. When JDK 28 ships (March 2027) it needs a rename or a roll tojdk-28. It is not pinned today, so the updater would propose 28 intojdk-27oncetemurin27-binariesis superseded. (In practice 28 ships from a different repo,temurin28-binaries, so the GithubRepo provenance alone probably never offers 28. A pin makes this explicit instead of relying on that.) Recommended follow-up in pkgmgr-rs: add a series pin todata/series_pins.toml:Vulnerability coverage
gominimal/minimal-supply-chain#514 adds a
jdk-27CPE identity (oracle:jdk+oracle:jre), the same as the mergedjdk-25entry. The provenance repotemurin27-binariesholds no advisories.Not verified here
I have not built this locally (house rule). I will comment
/buildto run the buildbot.🤖 Generated with Claude Code