Repository navigation
Releases
Releases · aoreshkov/kmp-wizard
v1.9.4
Added
- Generated projects open deep links on their own scheme.
myapp://my_features,myapp://my_features/new,myapp://my_features/{id},myapp://my_features/{id}/editandmyapp://settingsopen the matching screen on Android, desktop and iOS, with the screens a user would have passed through (such as the list) on the back stack. The scheme is the app name in flat lowercase (myappfor "My App"), because an underscore is not legal in a URI scheme and iOS rejects it. - Generated projects include a Bulgarian translation as an example of adding a language. The translation covers every UI string, Android 13 and later lists the app under the per-app language setting, and a new
checkStringResourceParitycheck fails the build when a language is missing a string. Your feature's Bulgarian text still describes the template's own feature, so itsvalues-bg/strings.xmland Bulgarian screen test begin with a note on how to translate it or remove Bulgarian.
Changed
- Generated projects need IntelliJ IDEA 2026.3 or Android Studio Quail 2 (2026.1.2) to open. They now use AGP 9.3.3 (up from 9.1.1), and older IDEs refuse it during Gradle sync. The plugin itself still installs on 2026.1 and later.
- Ledger pin bumped to
v1.11.0. Besides the deep links and the Bulgarian translation, generated projects get right-to-left layout tests for every screen, screen titles marked as headings for screen readers, desktop keyboard tests, and a fix that lets Tab leave the editor's multi-line text field instead of typing a tab character. Dependency upgrades: Kotlin 2.4.21, AGP 9.3.3, AndroidX DataStore 1.3.0, kotlinx.serialization 1.13.0, KSP 2.3.14, Robolectric 4.18.1 and Gradle 9.9.2.
v1.9.3
Changed
- Ledger pin bumped to
v1.10.0. Generated projects no longer double-submit or double-navigate on repeat taps: Save ignores taps while a save is in flight (no more duplicate postings in create mode), opening a posting or the editor is single-top, a double tap on a back button pops only its own screen, and re-selecting the current navigation-bar section scrolls its list to the top instead of discarding its back stack. Save and delete outcomes are now UI state rather than one-off events, so a result that lands during rotation or a section switch is no longer lost, error snackbars don't reappear, and the delete confirmation dialog survives rotation. Dependency upgrades: Compose Multiplatform 1.12.2, Material3 Adaptive 1.3.0 (stable),navigation3-ui1.2.0-rc01 andnavigation3-runtime1.2.0. Because the edit screen's state now declaresisSavingandisSavednext to your field, the field namesis_savingandis_savedare rejected. - Multi-word feature names produce idiomatic camelCase Kotlin identifiers. A feature named
my_featureused to generatemy_featureDao,val my_featuresandmy_feature1; it now generatesmyFeatureDao,myFeaturesandmyFeature1. Packages, module directories, resource keys and database table names keep the snake_case form. Projects with a one-word feature are unchanged.
Fixed
- Projects whose name starts with a digit or has no Latin letters now generate valid class names and plugin IDs. A project named
2048used to produceclass 2048App, andПроектproduced the plugin ID.kotlin.multiplatform. The code names are now repaired (App2048,MyApp), while the project directory keeps the name you typed. - Field names that clash with the generated model are rejected. Names such as
id,updated_at,is_validorsave(which collides with the generatedsaveError) used to produce a project that doesn't compile. Both the IntelliJ IDEA form and the Android Studio path now say which generated member the name clashes with. - Android Studio: the package name is validated like it is in IntelliJ IDEA. Studio's own check accepts packages such as
com.example.fun(a Kotlin keyword) orcom.example.my_app(which breaks the iOS and desktop bundle IDs). The wizard now stops before generating anything and names the problem. - Deselected platforms and unlicensed Pro files can no longer slip into a project. If a file inside them can't be deleted, for example because antivirus holds it open, generation now fails cleanly instead of leaving the folder behind.
- Cancelling after the files are written now tells you the project exists. A Cancel during the Gradle link used to leave a project that was never linked, with no message. You now get a notification that tells you to finish with Link Gradle Project.
- A temporary backup folder that can't be removed is reported instead of being silently left inside the new project.
- Pro features follow your license at generation time in IntelliJ IDEA, as they already did in Android Studio. Before, the wizard used the entitlement it read when the dialog opened.
- Android Studio: a leftover marker from an aborted run no longer makes the wizard write the project during Studio's dry run. The post-sync
apiDumplistener is also dropped if the first sync never happens, and regenerating into the same folder no longer runsapiDumptwice.
v1.9.2
Changed
- Ledger pin bumped to
v1.9.1. Generated projects move to Kotlin 2.4.20, which is officially tested with the AGP 9.1.1 they pin. Other dependency upgrades: Compose Multiplatform 1.12.1, with Material3 Adaptive 1.3.0-rc01 andnavigation3-ui1.1.2 aligned to it, KSP 2.3.12 (the KSP pin is gone), Kover 0.9.11, Logback 1.6.5 (fixes CVE-2026-104721, which generated projects can't reach because they configure no MDC discriminator), SLF4J 2.0.20 /slf4j-android2.0.20-0, and the Gradle wrapper 9.8.0.
Fixed
- Kotlin and Java keywords are rejected as package segments and as feature or field names. Names like
com.example.objector a field calledvalused to pass validation and produce a project that doesn't compile. The wizard now flags them as you type. The package it proposes from the project name is always valid too, so a project named "Object", "Class" or "2FA" no longer gets a broken default. - Android Studio: invalid feature and field names no longer produce an unbuildable project. Names are normalized (
My Featurebecomesmy_feature). A name that can't become a valid identifier, such as2fa, a non-Latin name or a keyword, stops generation with a notification that names the field, instead of reporting success. - Quotes, backslashes and
$in the test value are escaped. A value likeSay "hi"used to break the generated tests, andcost $5changed their meaning. - Stray spaces in the package name no longer reach generated packages and directories.
- A failed generation no longer leaves a half-written or emptied project directory. Writing the project into its folder now either finishes or is rolled back. If it fails part-way, for example on a full disk or a file locked by antivirus, every file it wrote is removed and every file it replaced is put back. In Android Studio, the default project files are only replaced after rendering succeeds, and are restored if the write fails.
- The post-sync
apiDumpruns at most once, even when two sync events arrive at the same moment.
v1.9.1
Changed
- Ledger pin bumped to
v1.9.0. Generated projects now declare their domain models andListstable to the Compose compiler (compose_stability.conf), so composables that take them can skip recomposition, and the selected top-level section survives process death on Android. Dependency upgrades: Room 3.0.3,androidx.sqlite2.7.1, Kermit 2.2.0, Robolectric 4.17 (Android host tests now run on API 37), the Koin compiler plugin 1.2.1 (desktop compile-time graph checks re-enabled), KSP 2.3.10 and the Gradle wrapper 9.7.1. DataStore now comes from the-coreartifacts the KMP guide names.LabeledFieldtakes amodifierparameter, and Kover's coverage floors are higher now that Room's generated code is excluded.
Fixed
- The hot-reload MCP server in the generated
.mcp.jsonnow starts on Windows. It launches through the Gradle wrapper JAR instead of./gradlew, so thegradlew.batworkaround 1.9.0 described is no longer needed. - Generated projects' DataStore settings recover from corruption on iOS as well as on Android and desktop.
- Android backup rules now exclude whole domains as intended, and the opt-in Compose compiler reports (
-Pledger.composeCompilerReports=true) are written as readable files on Windows instead of hidden NTFS streams.
v1.9.0
Added
- Generated projects get Compose Hot Reload on desktop.
./gradlew :desktopApp:hotRunapplies composable edits to the running window without a restart, so UI iteration no longer costs a full relaunch. The hot-run JVM is provisioned automatically (a JetBrains Runtime is downloaded and cached under<GRADLE_USER_HOME>/chr/jbrfor that JVM only — it ships the enhanced class redefinition hot reload needs), while ordinary compilation keeps using the project's daemon JDK. The same plugin also contributes:desktopApp:hotMcpServerand a repository-level.mcp.json, which lets a coding agent reload, screenshot, read the semantic tree and drive the running app — on Windows that server entry needs thegradlew.batform registered locally, since the checked-in config invokes./gradlew.
Changed
- Ledger pin bumped to
v1.8.0. Generated projects move to Compose Multiplatform 1.12.0 (from 1.11.1), with Material3 and the Material3 Adaptive Navigation Suite on the aligned 1.12.0-alpha03, plus Room 3.0.2, Navigation 3 runtime 1.1.7, binary-compatibility-validator 0.18.2 and SLF4J 2.0.19. - The desktop window adopts the Compose Window API v2 (
androidx.compose.ui.window.v2): initial bounds come from a bounds provider and the minimum size is Dp-typed. The API is still experimental and its package may move before it stabilizes, so expect an import change — not a rewrite. - Generated build files are tidier and quieter. The AGP 9.1.1 and Kotlin 2.4.0 pins are now documented and suppressed in the version catalog (both are deliberately held at what the bundled IDE plugin supports, so currency inspections and Dependabot no longer flag them), the Koin convention plugin sets
aiAssist = falseto silence a vendor call-to-action during compilation, andandroidApp's unused local unit-test configuration is gone.
Fixed
- The desktop window's minimum size now scales with display density. It was previously applied through AWT in unscaled device pixels, so on a 200%-scaled display the floor was half its intended physical size while the initial size scaled correctly.
- New desktop windows open centred on screen instead of cascading from the last window position, which on a multi-monitor setup could place a new window on whichever display the previous one had used.
- The plugin no longer uses a deprecated IntelliJ Platform API.
KMPWizardBundlenow delegates to aDynamicBundleinstance rather than inheriting from one: theDynamicBundle(String)constructor a subclass needs carried only@Obsoletethrough 2026.2 and became a real@Deprecatedin 2026.3, where the Plugin Verifier began reporting it — so the Marketplace flagged one deprecated API usage against an otherwise compatible 1.8.0. Message resolution is unchanged, and no call sites changed.
v1.8.0
Added
- Generated projects now ship a
.gitattributes. It normalizes text files to LF on commit, pinsgradlewand theapiDumpABI dumps to LF in the working tree, and leavesgradlew.batand binary assets unconverted — so a Windows checkout no longer reports every ABI dump as modified after a build, and the wrapper script still runs under Git Bash and WSL. Like.gitignore, the file is stored in the plugin jar under a neutral name (gitattributes.txt) because Gradle's Ant default excludes would otherwise drop it, and is renamed back on render; the rename table replaces the previous one-off.gitignorespecial case.
Changed
- Ledger pin bumped to
v1.7.0. The generated data layer becomes replication-ready: the entity carriesupdatedAt,isDeletedandpendingSyncsync metadata that never reaches the domain model, deletes are soft (a tombstoned row is hidden from reads but retained so the deletion can propagate), and the repository stamps the last-write-wins timestamp on every local write from an injectedkotlin.time.Clock— which also makes those writes deterministically testable. The DAO gains the replication-facing queries that contract implies (getPendingSync,getByIds,upsert,clearPendingSyncIfUnchanged), each covered by tests.core:navigationaddsLocalAccountAction, an app-bar slot that renders nothing unless the app root provides one, so a feature screen can surface an account action without depending on an auth feature. Versions move to Navigation 3 runtime1.1.6, Logback1.6.3and Bouncy Castle1.85.2, and the CI workflow action pins are refreshed.
v1.7.1
Changed
- Ledger pin bumped to
v1.6.5. Generated projects now pinpackageOfResClassin every module that generates a ComposeResclass, so their resource accessors sit under<your.package>.<module path>.resourcesinstead of a package derived from the project name — renaming the root project can no longer repackage every module's resources at once. They also move to the Koin compiler1.1.0, which verifies the whole dependency graph once at each@KoinApplicationentry point rather than module by module, and pick up Navigation 3 runtime1.1.5, Room3.0.1and Logback1.6.1.
Fixed
- Generated projects no longer fail to compile when the project name is more than one word. Compose Multiplatform derives the package of its generated
Resaccessor class from the Gradle project group, which in turn comes fromrootProject.name— lowercased with the words run together. The wizard was rendering thoseimportstatements in snake_case instead, so a project namedMy Awesome Appimportedmy_awesome_app.feature.…from a package actually calledmyawesomeapp.feature.…, and every screen and DI module that reads a string resource failed to resolve. Single-word project names were unaffected, which is why this went unnoticed.
v1.7.0
Added
- The wizard now appears in Android Studio. Android Studio replaces the platform's New Project dialog with its own, template-driven one, which never showed the wizard no matter how it was configured — the plugin installed, loaded, and offered nothing. It is now also contributed as an Android Studio project template, so it shows up under File | New | New Project in the Phone and Tablet gallery. Android Studio owns its first page, so project name, package name and save location come from there; the feature name, field name, test value, target platforms and Pro options follow on the next page. The IntelliJ IDEA entry point is unchanged. The same template also appears in IntelliJ IDEA when the Android plugin is installed.
Changed
- Minimum supported IDE lowered back to 2026.1 (
sinceBuild262 → 261), reverting the 1.6.1 bump. Android Studio runs a full platform branch behind IntelliJ IDEA — the newest Android Studio on any channel is stillAI-261.*— so a 262 floor made the plugin impossible to install in every existing Android Studio. The AGP concern behind the 1.6.1 bump does not apply to Android Studio, whose bundled tooling is AGP 9.3.1, well above the 9.1.1 that generated projects use. - The plugin is now compiled against IntelliJ IDEA 2026.1 rather than 2026.2, so the compile-time API surface matches the declared
sinceBuild. - Ledger pin bumped to
v1.6.4. Generated projects move to Logback1.6.0on desktop (the 1.6.x line targets the SLF4J 2.0.18 baseline the project already pins), pick up refreshed GitHub Actions pins in their CI workflows (actions/checkoutv7.0.1,ossf/scorecard-actionv2.4.4,github/codeql-action/upload-sarifv4.37.3), and ship README /CLAUDE.mdtech-stack tables that match their own version catalog.
v1.6.1
Changed
- Requires IntelliJ IDEA / Android Studio 2026.2+: the minimum supported IDE moves up (
sinceBuild261 → 262). This lets generated projects target the newest Android Gradle plugin that the IntelliJ Android plugin accepts, instead of being held back to the 2026.1 ceiling. - Ledger pin bumped to
v1.6.3. - Marketplace listing: the plugin description now includes a Free-vs-Pro comparison table and links to the open-source repository (source code, issue tracker, documentation) — visible on the Marketplace page and in the IDE Plugin Manager. No functional changes.
Fixed
- Generated projects no longer fail Gradle sync with "incompatible version (AGP 9.2.1)": on IntelliJ IDEA 2026.2 the bundled Android plugin supports the AGP 9.1 line, but generated projects shipped AGP 9.2.1 (from the pinned kmp-ledger release) and sync was refused. The ledger pin now provides AGP 9.1.1 — within the line the IntelliJ Android plugin accepts — so sync succeeds.
v1.6.0
Added
- Community & CI scaffolding in generated projects:
CONTRIBUTING.md,CODE_OF_CONDUCT.md, an OpenSSF Scorecard workflow, a dependency-submission workflow, andandroidApp/proguard-rules.pro— picked up from the kmp-ledgerv1.5.0release. - API dumps generated from the user's code: after the generated project's first Gradle sync, the wizard runs
apiDumpin the background so the binary-compatibility dumps under<module>/api/reflect the project's own package, app, and feature names. If the run fails, a notification points to./gradlew apiDump. - Repository support & ownership files: a
SUPPORT.mdrouting questions to the right channels (issues, kmp-ledger, Marketplace, private contact) and aCODEOWNERSfile.
Changed
- Source license clarified — MIT: the plugin's source code is published under the MIT license. The plugin as distributed on JetBrains Marketplace (Free/Pro tiers) remains governed by its EULA.
- Templates now come from the published kmp-ledger release: the plugin's project templates are generated at build time from the pinned kmp-ledger release tag, so generated projects always match a public, tagged state of the reference app.
- Ledger pin bumped to
v1.6.2.
Fixed
- No half-built projects on cancel or failure: generation now runs in an isolated staging directory and is committed to the project folder only after it fully succeeds — cancelling the wizard or hitting a generation error leaves the project directory untouched.
- No more maintainer-local files in generated projects: the previous template snapshot could pick up files that existed only in the maintainer's working copy (internal review documents under
docs/, a localgradle-daemon-jvm.properties); generating from the published release tag makes that impossible. - Generated projects no longer fail
checkon stale API dumps: the templates used to ship the ledger's*.api/*.klib.apidumps with placeholder substitution applied. Dumps are compiler-output snapshots — compiler-generated symbol names, declaration sort order, and Compose lambda keys all derive from the original names — so the substituted copies could never match a freshapiDump, and./gradlew check(apiCheck) failed in any project not named exactly like the ledger. Dump files are now excluded from the templates entirely (see theapiDump-after-sync entry above). - No sponsor button on generated repos: the ledger's
.github/FUNDING.yml(its own sponsor config) is no longer copied into templates.
Security
- CodeQL code scanning: a CodeQL workflow analyzes the plugin's Kotlin/JVM sources on every push, pull request, and weekly schedule.
- CI actions pinned to commit SHAs: all GitHub Actions in the build and CodeQL workflows are pinned to full commit SHAs (supply-chain hardening, per GitHub's Actions security guidance); Dependabot keeps the pins current.