Skip to content

fix: pin apiVersion/languageVersion to 2.1, release beta20 - #58

Merged
aldefy merged 1 commit into
mainfrom
chore/vanniktech-publish
Aug 20, 2026
Merged

aldefy merged 1 commit into
mainfrom
chore/vanniktech-publish

Conversation

@aldefy

@aldefy aldefy commented Aug 20, 2026

Copy link
Copy Markdown
Owner

Fixes: beta19's Kotlin 2.3.0 toolchain bump was forcing that version onto every consumer app — published metadata was stamped mv=[2,3,0], unreadable by older Kotlin compilers.

Pinned apiVersion/languageVersion to KOTLIN_2_1 in lumen/build.gradle.kts. Lumen still builds with the 2.3.0 toolchain, but emits 2.1-compatible metadata. Verified via javap on the built jar — kotlin.Metadata.mv now reads [2,1,0].

Consumers on Kotlin 2.1+ can depend on this release. 2.1 is the new floor, not "any version." apiCheck passes clean — no public API surface changed.

Bumps to 1.0.0-beta20.

… force onto consumers

beta19's Kotlin 2.3.0 bump stamped published metadata mv=[2,3,0], which
older Kotlin compilers can't read at all. Pin the compiler's
apiVersion/languageVersion to 2.1 so lumen still builds with 2.3.0 but
emits 2.1-compatible metadata. Verified via javap on the built jar's
kotlin.Metadata annotation.

Bump to 1.0.0-beta20.
@aldefy
aldefy force-pushed the chore/vanniktech-publish branch from 224705a to 1b4216f Compare August 20, 2026 07:37
@aldefy
aldefy merged commit 7393036 into main Aug 20, 2026
6 checks passed
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