[Skumring]

Pin the JitPack build to JDK 11.

Without a jitpack.yml JitPack picks its own build image. The current one fails before Gradle starts (JAVA_HOME is set to an invalid directory: /usr/lib/jvm/jdk-11), which is why 4.1.2 could not be built. The same file is already on release-4.1 and 4.1.3 is built with it.

JDK 11 matches sourceCompatibility / targetCompatibility in build.gradle.kts.

Summary by CodeRabbit

• Chores
  • Updated the JDK used for JitPack builds to OpenJDK 11.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: ec0ffe2e-ac7c-4d38-a9bc-99db870642d8

📥 Commits

Reviewing files that changed from the base of the PR and between ce7337d and 12c7bc5.

📒 Files selected for processing (1)

• jitpack.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The JitPack configuration now selects OpenJDK 11.

Changes

JitPack Build Configuration

Layer / File(s)	Summary
Select the JDK jitpack.yml	The configuration specifies OpenJDK 11.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 12c7b

This change selects Java 11 for JitPack, consistent with the project’s target, and the configured Gradle version supports that runtime. No actionable merge risk is established.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: pinning the JitPack build to JDK 11.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}