Skip to content

Hold java on Adoptium mainline LTS via a renovate rule that actually matches #78

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dfalling merged 1 commit into from
Aug 21, 2026
Merged

Hold java on Adoptium mainline LTS via a renovate rule that actually matches #78

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions renovate.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,10 @@
"extends": ["config:recommended"],
"packageRules": [
{
"description": "Keep java on Adoptium mainline builds. Adoptium also publishes interim respins (`jdk-25.0.4.1+1`), and it builds those only for the platforms that needed the fix — 25.0.4.1 shipped for alpine-linux/x64 and mac/x64 only, with no linux/x64 binary. mise resolves java per platform, so a respin that skips linux/x64 has no metadata there at all and `mise install` hard-fails (`no metadata found for version temurin-25.0.4+101.0.LTS`), breaking CI and every dev machine that isn't a mac x64. Adoptium's semver maps a respin as `patch * 100 + build`, so mainline builds always land under +100 and respins at +1xx and up — that's what this regex excludes. Mainline updates (25.0.5, 26, ...) ship for all platforms and still come through. Drop this rule if Adoptium starts building respins for every platform.",
"matchPackageNames": ["java"],
"description": "Hold java on Adoptium mainline LTS builds, matched on depName: the mise manager reports this dep as depName `java` but packageName `java-jdk`, and matchPackageNames tests the packageName, so a matchPackageNames: [\"java\"] rule silently never applies. The regex admits only mainline LTS builds and blocks two things. First, Adoptium's interim respins (`jdk-25.0.4.1+1`): Adoptium builds a respin only for the platforms that needed the fix, and 25.0.4.1 shipped alpine-linux/x64 and mac/x64 only, with no linux/x64 binary. mise resolves java per platform, so on linux/x64 there is no metadata at all and `mise install` hard-fails (`no metadata found for version temurin-25.0.4+101.0.LTS`) before any build step, breaking CI and every dev machine that isn't a mac x64. Adoptium's semver encodes a respin as `patch * 100 + build`, so respins land at +1xx and up while mainline builds stay under +100 — hence the 1-2 digit build. Second, non-LTS majors (`26.0.2+10`, no LTS suffix): this is the Android build JDK and tracks LTS only. Mainline LTS patches (25.0.5, and the next LTS when it ships) still come through.",
"matchDepNames": ["java"],
"matchManagers": ["mise"],
"allowedVersions": "!/\\+\\d{3,}\\./"
"allowedVersions": "/^\\d+\\.\\d+\\.\\d+\\+\\d{1,2}\\.0\\.LTS$/"
},
{
"description": "Pin Gradle to <9.7. React Native 0.87.0's bundled gradle-plugin (node_modules/@react-native/gradle-plugin) is compiled with Kotlin 2.2.0, whose compiler can only read Kotlin metadata up to 2.3.0. Gradle >=9.7 bundles a Kotlin 2.4.0 stdlib/reflect that leaks onto the settings-plugin compile classpath, so the build fails compiling the RN plugin (`Module was compiled with an incompatible version of Kotlin`). 9.6.1 is the highest version verified to configure cleanly; the wrapper tracks 9.4.1, the version RN 0.87 itself ships and builds against. Raise this ceiling once React Native ships a gradle-plugin built with Kotlin >=2.3.",
Expand Down
Loading