Bzlmod Workflow for developing against an updated `released_` rules_kotlin?

[erikkerber]

rules_kotlin uses rules_kotlin to build and bootstrap itself. It does this by pulling in earlier releases of the ruleset

During development, what is the best way to change the "released" version? If I just swap out the @released_rules_kotlin with the current repository, it just yields circular dependencies.

How do the maintainers work with this?

EDIT

The README speaks to this a bit in the context of WORKSPACE. I couldn't (quickly) figure out if this was possible with bzlmod setups and local_repository.

[restingbull]

You mean to use the in development rules_kotlin? Or that the bootstrap module is old?

[erikkerber]

Concretely—I wanted to just plug in Kotlin 2.1.0-RC2 to see if the issues with 2.0.20 were resolved (2.0.20 failed with a class load error in Kotlin libraries themselves).

Using bzlmod, and pointing to a local version of rules_kotlin with these changes, rules_kotlin then downloads the last released version of rules_kotlin (1.9), and bootstraps itself with that. Doing that results in errors like:

external/rules_kotlin+/src/main/kotlin/io/bazel/kotlin/plugin/SkipCodeGen.kt:77:29: error: class 'org.jetbrains.kotlin.analyzer.AnalysisResult.Companion' was compiled with an incompatible version of Kotlin. The actual metadata version is 2.1.0, but the compiler version 1.9.0 can read versions up to 2.0.0.

My understanding is that the "released" Kotlin is not compatible with my local development version. What I'm not sure how to do is to shim out the released Kotlin with, I guess, what is essentially my local version as well.

[restingbull]

That issue is blocking the 2.0.20 release. :/

Recent changes made it happen before we cut the release, as opposed to after.

I'm currently trying to sort out the stdlib + compiler plugin issues to unblock this.

[erikkerber]

Resolved with #1244

Thanks @restingbull!