[Skumring]

Release 4.1.3: publishes the 4.1.1 changes and pins the JitPack JDK.

JitPack could not build 4.1.2: without a jitpack.yml it picks its own build image, and the current one fails before Gradle starts (JAVA_HOME is set to an invalid directory: /usr/lib/jvm/jdk-11). Earlier releases were built on an image where JDK 11 was present.

Commits

1. jitpack.yml with jdk: openjdk11 (matches sourceCompatibility = 11), version bump to 4.1.3 and CHANGELOG entry. No code changes since 4.1.1.

Checks

CI runs on this PR. The JitPack build command (./gradlew clean -Pversion=4.1.3 -xtest assemble publishToMavenLocal) passes on JDK 11, including javadoc.

After merge

Tag 4.1.3 on release-4.1 and create the GitHub release; JitPack builds from the tag.

[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]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 1a76cec8-91bf-44b1-9a9a-82d3d8eac719

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• 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.}