Prepare to release 0.1.1 (#9)

Author: skydoves

CHANGELOG.md

@@ -5,12 +5,15 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased]
+## [0.1.1] - 2026-06-13
 
 ### Added
 - **`@Preview(locale = …)` support for thumbnails** ([#7](https://github.com/skydoves/compose-nav-graph/issues/7)): the KSP processor now captures the preview's locale qualifier (declared directly or via a multipreview meta-annotation) into the manifest, and both render backends apply it (Layoutlib through the renderer's preview params, Robolectric through a composition-scoped configuration-context override), so localized previews render with the same resources Android Studio shows.
+- **`navgraph { robolectricApplication }`** ([#6](https://github.com/skydoves/compose-nav-graph/pull/6), thanks [@pesjak](https://github.com/pesjak)): point the Robolectric render at a minimal test-only `Application` (emitted as `@Config(application = …)` on the generated render test), so apps that initialize device-backed SDKs in `Application.onCreate` can render thumbnails.
 
 ### Fixed
+- **Gradle configuration cache compatibility** ([#4](https://github.com/skydoves/compose-nav-graph/pull/4), thanks [@pesjak](https://github.com/pesjak)): the render wiring no longer captures `TaskProvider`s in the unit-test task's `onlyIf` spec, so `generateNavGraph` and the export tasks run with the configuration cache enabled (no more `--no-configuration-cache`).
+- **Single-module Compose Multiplatform apps** ([#5](https://github.com/skydoves/compose-nav-graph/pull/5), thanks [@pesjak](https://github.com/pesjak)): a module that is both KMP and `com.android.application` (the KMP wizard default) now renders thumbnails from its own linked resources instead of skipping them.
 - The generated `navgraph.version` resource (which pins the auto-wired `compose-nav-graph-annotations` / `compose-nav-graph-ksp` / `compose-nav-graph-testing` versions) is regenerated when `VERSION_NAME` changes instead of staying stale.
 
 ## [0.1.0] - 2026-06-01

README.md

@@ -90,7 +90,7 @@ Then apply the plugin and KSP to the module that holds your screens. That's all.
 // build.gradle.kts
 plugins {
     id("com.google.devtools.ksp") version "<matching your Kotlin version>"
-    id("com.github.skydoves.navgraph") version "0.1.0"
+    id("com.github.skydoves.navgraph") version "0.1.1"
 }
 ```
 

compose-nav-graph-gradle/gradle.properties

@@ -1,7 +1,7 @@
 # compose-nav-graph-gradle is a standalone (included) build, so it carries its own publishing coordinates
 # rather than inheriting the root gradle.properties.
 GROUP=com.github.skydoves
-VERSION_NAME=0.1.1-SNAPSHOT
+VERSION_NAME=0.1.1
 
 POM_NAME=Compose Navigation Graph Gradle Plugin
 POM_ARTIFACT_ID=compose-nav-graph-gradle

docs/gradle-plugin/getting-started.md

@@ -29,7 +29,7 @@ Apply the plugin together with [KSP](https://github.com/google/ksp) in the `buil
 ```kotlin
 plugins {
     id("com.google.devtools.ksp") version "<ksp-version>"
-    id("com.github.skydoves.navgraph") version "0.1.0"
+    id("com.github.skydoves.navgraph") version "0.1.1"
 }
 ```
 
@@ -46,7 +46,7 @@ If you keep plugin versions in `libs.versions.toml`:
 ```toml
 [plugins]
 ksp = { id = "com.google.devtools.ksp", version = "<ksp-version>" }
-navgraph = { id = "com.github.skydoves.navgraph", version = "0.1.0" }
+navgraph = { id = "com.github.skydoves.navgraph", version = "0.1.1" }
 ```
 
 ```kotlin

docs/index.md

@@ -34,7 +34,7 @@ In your app (or feature) module's `build.gradle.kts`, apply the navgraph plugin
 ```kotlin
 plugins {
     id("com.google.devtools.ksp") version "<ksp-version>"
-    id("com.github.skydoves.navgraph") version "0.1.0"
+    id("com.github.skydoves.navgraph") version "0.1.1"
 }
 ```
 

docs/kotlin-multiplatform.md

@@ -9,7 +9,7 @@ KMP specific configuration: you apply the same two plugins as on a plain Android
 // shared/build.gradle.kts
 plugins {
     id("com.google.devtools.ksp") version "<matching your Kotlin version>"
-    id("com.github.skydoves.navgraph") version "0.1.0"
+    id("com.github.skydoves.navgraph") version "0.1.1"
 }
 ```
 

gradle.properties

@@ -13,7 +13,7 @@ android.nonTransitiveRClass=true
 
 # --- Maven coordinates (vanniktech publish) ---
 GROUP=com.github.skydoves
-VERSION_NAME=0.1.1-SNAPSHOT
+VERSION_NAME=0.1.1
 
 POM_URL=https://github.com/skydoves/compose-nav-graph/
 POM_SCM_URL=https://github.com/skydoves/compose-nav-graph/

samples/sample-kotlinconf/README.md

@@ -25,7 +25,7 @@ End user setup is intentionally minimal: **applying the plugin auto wires `compo
 ```kotlin
 plugins {
     id("com.google.devtools.ksp") version "<matches your Kotlin version>"
-    id("com.github.skydoves.navgraph") version "0.1.0"
+    id("com.github.skydoves.navgraph") version "0.1.1"
 }
 ```
 

samples/sample-kotlinconf/app/shared/build.gradle.kts

@@ -16,7 +16,7 @@ plugins {
     alias(libs.plugins.hotswan.compiler)
     alias(libs.plugins.metro)
     id("com.google.devtools.ksp") version "2.3.9"
-    id("com.github.skydoves.navgraph") version "0.1.0"
+    id("com.github.skydoves.navgraph") version "0.1.1"
 }
 
 kotlin {

samples/sample-nowinandroid/gradle/libs.versions.toml

@@ -53,7 +53,7 @@ kotlinxSerializationJson = "1.8.0"
 ksp = "2.3.4"
 ktlint = "1.4.0"
 hotswan = "1.3.4"
-navgraph = "0.1.0"
+navgraph = "0.1.1"
 okhttp = "4.12.0"
 protobuf = "4.29.2"
 protobufPlugin = "0.9.6"