ci(jitpack): pin JDK 17 and scope install to the library module#73
Merged
Conversation
JitPack built on openjdk21 while the release verify/javadoc gate runs on JDK 17 (the project's maven.compiler.release baseline), so the published jar was built on a JDK that CI does not validate. Pin JitPack to openjdk17 to remove that drift, and scope the install to `-pl .` so only the library artifact is built, never the examples/benchmarks reactor siblings.
2 tasks
DemchaAV
added a commit
that referenced
this pull request
May 29, 2026
…ase.yml (#74) Updates the release runbook to match the v1.6.5 plumbing (#69 #70 #71 #72 #73): - README install snippets now flip in the release commit (cut-release.ps1), enforced by VersionConsistencyGuardTest — replaces the old "stay pinned to the previous tag, flip post-release" model that contradicted the guard. - Version lives in four sites (library pom, aggregator, inherited examples/benchmarks parents); the script bumps all four + README in one pass. - GitHub Release is created automatically by release.yml on tag push; the manual gh release create is now the documented fallback. - Adds VersionConsistencyGuardTest to the pre-release guard-suite gate, and a v1.6.5 lesson that supersedes the v1.6.0 graphcompose.version property note. The graphcompose-release-engineer skill (local config, Claude + Codex copies) was aligned in lockstep.
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.
Summary
jitpack.yml:openjdk21→openjdk17, andinstallscoped to-pl ..Why
JitPack built the published jar on openjdk21 while the release verify/javadoc gate runs on JDK 17 (the project's
maven.compiler.releasebaseline) — the artifact consumers download was built on a JDK CI doesn't validate. Pinning to 17 removes that drift. Scoping install to-pl .builds only the library, never the examples/benchmarks reactor siblings.Test plan
jitpack.ymlparses (jdk: [openjdk17], install: [...-pl .])./mvnw -B -ntp -DskipTests install -pl .→ BUILD SUCCESS, installs only graphcompose (library + tests jar), no siblings