ci: pin ORT to 88.0.0 on JDK 21 (fix ORT Compliance) - #22
Merged
Conversation
The "Install ORT" step downloads ORT's floating releases/latest. ORT's current release targets Java 25 (class file 69.0), but the job pinned setup-java to JDK 21 (class file 65.0), so `ort` failed at launch with UnsupportedClassVersionError on every PR. Bump the runtime JDK to 25 to match. Comment added so the coupling to ORT's floating latest is explicit. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Amends the JDK-25 approach. ORT 89.0.0+ raised its launch baseline to
Java 25, but even under JDK 25 its bundled Gradle Inspector (Gradle 8.13)
cannot parse Java 25 bytecode ("Unsupported class file major version 69"),
so bumping the runner JDK only moves the failure downstream. Instead pin
ORT to 88.0.0 — the last release that both launches and resolves the
Gradle project on JDK 21 (the combo that was green on main on 2026-06-10)
— and keep setup-java at 21. Replaces the floating releases/latest with a
tagged download so the toolchain is reproducible.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
kbennett2000
changed the title
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
1 participant
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.
Problem
ort-analyze-reportin ORT Compliance fails on every PR (and would onmain). The job downloaded ORT's floatingreleases/latest, and ORT moved out from under JDK 21:UnsupportedClassVersionError(class file 69.0) under the pinned JDK 21.app/build.gradle→Unsupported class file major version 69. Chasing the JDK baseline just moves the break downstream.This is repo-wide CI drift from the floating
latest, not from any app change. It surfaced on #21 (a docs-only PR).Fix
Pin ORT to
88.0.0— the last release that both launches and resolves the Gradle project on JDK 21 (the exact combo that was green onmainon 2026-06-10, whenlatesthappened to be 88.0.0). Keepsetup-javaat 21. Swapping the floatingreleases/latestfor a taggedreleases/tags/88.0.0download also makes the toolchain reproducible. A comment documents when to revisit (once ORT's Gradle Inspector supports Java 25).Verify
This PR exercises the changed workflow; its own ORT Compliance check is the test.
🤖 Generated with Claude Code