analysis-api-bump

Solid

Bump the Kotlin version together with the version-locked Analysis API `-for-ide` artifacts and their runtime-dep pins, then verify source analysis still works. Use when upgrading Kotlin, when the Analysis API fails to resolve types after a bump, or when auditing whether the coupled pins are still correct.

API & Backend 10 stars 0 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 82/100

Stars 20%
35
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Bump Kotlin + Analysis API (version-locked) The Analysis API (standalone K2/FIR) is the single most version-fragile part of this repo. Kotlin and every `*-for-ide` artifact **must share the exact same version**, and two runtime deps (`caffeine`, `intellijCoroutines`) are pinned to match what the bundled IntelliJ core expects. Getting this wrong shows up as `NoSuchMethodError` / `NoClassDefFoundError` at runtime or as silent loss of type resolution — never a clean compile error. Follow the steps; do not eyeball it. ## 1. Snapshot the current pins Read `gradle/libs.versions.toml` and record: - `kotlin` — the shared version ref used by **all** of: `analysisApi-standalone`, `analysisApi-highLevel`, `analysisApi-k2`, `analysisApi-lowLevelFir`, `analysisApi-implBase`, `analysisApi-platform`, `analysisApi-symbolLightClasses`, `kotlin-compiler`, plus the `kotlin-*` / `composeCompiler-*` plugin artifacts. - `caffeine` (comment: "runtime dep of the Analysis API `-for-ide` jars; matches Kotlin's own pin"). - `intellijCoroutines` (comment: "JetBrains coroutines fork the bundled IJ core expects (KT-81457)"). - `compose` (comment: "aligned to Kotlin X.Y.Z") — Compose is Kotlin-coupled too. Because every Analysis-API artifact uses `version.ref = "kotlin"`, bumping the single `kotlin` entry moves them all. The risk is **not** forgetting one artifact — it's the three coupled satellites (`caffeine`, `intellijCoroutines`, `compose`) and undocumented API breaks. ## 2. Confirm the t...

Details

Author
aoreshkov
Repository
aoreshkov/kotlin-lib-mcp
Created
2 months ago
Last Updated
today
Language
Kotlin
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

bump-dependencies

Bump every third-party dependency, plugin and toolchain pin in VibeTags to its latest stable release, mirror the pins Gradle cannot inherit, verify with the real gates, and open the PR. Use when the user says "bump dependencies", "update dependencies", "dependency update", "upgrade deps", "are we on the latest versions", or before a release.

25 Updated today
PIsberg
AI & Automation Listed

bump-versions

Bump dependency versions in Gradle version catalogs, Kotlin Toolchain catalogs, and Maven POMs using caupain or the Maven Versions Plugin.

0 Updated 1 months ago
sureshg
Data & Documents Featured

very-good-analysis-upgrade

Upgrade the very_good_analysis lint package to a new version in any Dart or Flutter package, handling the pubspec.yaml version bump, the lint fixes the new rules force, and the PR. Trigger on phrases like "bump very_good_analysis to 10.0.0", "upgrade very_good_analysis", "update our lint package", "we're due for a lint upgrade", "take very_good_analysis to the latest", or a `dart pub get` conflict reported after a very_good_analysis bump. Use it even when the user only describes the package instead of pointing at it, because the decisions it governs are scope calls that do not need the files on disk: which constraint to write, which warnings to fix, and what stays out of the PR. The trigger is a very_good_analysis version change. A conflict surfaced by a Dart or Flutter SDK bump belongs to dart-flutter-sdk- upgrade instead, even when very_good_analysis is the package blocking resolution.

165 Updated 4 days ago
VeryGoodOpenSource