Skip to content

chore: take kbuild 1.2.10 - #17

Merged
rasros merged 1 commit into
mainfrom
chore/kbuild-1.2.10
Aug 9, 2026
Merged

chore: take kbuild 1.2.10#17
rasros merged 1 commit into
mainfrom
chore/kbuild-1.2.10

Conversation

@rasros

@rasros rasros commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Summary

com.eignex.* pins move to 1.2.10.

Why

1.2.10 carries two fixes, both of which matter here.

detekt goes back to 2.0.0-alpha.3. Neither newer alpha is usable across the fleet: alpha.5 reports
documented constructor parameters as undocumented, and alpha.6 reports used private constructor
properties as unused. alpha.3 is the last version clean in every repo.

The plugin jar now emits Java 21 bytecode while still compiling on 25, so it declares
"org.gradle.jvm.version": 21 instead of 25. Gradle reads that during dependency resolution, so
1.2.8 and 1.2.9 could only be resolved by a Gradle daemon running JDK 25. 1.2.10 drops that floor
back to 21 while consumer code still targets 25 through jvmToolchain(25).

CI stays on JDK 25, which is still needed for the toolchain. What changes is local development: a
build no longer refuses to resolve the plugin on JDK 21 or 22.

Testing

CI. kbuild 1.2.10 was verified before release with a release-workflow dry run and
samples/smoke-test.sh, and after release against the published artifact: every class in
kbuild-1.2.10.jar is major 65, and the module metadata declares "org.gradle.jvm.version": 21.

@rasros
rasros merged commit 4e7fd00 into main Aug 9, 2026
1 check passed
@rasros
rasros deleted the chore/kbuild-1.2.10 branch August 9, 2026 04:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant