Release v1.0.0

[kirich1409]

Release v1.0.0 — develop → main

First stable release of Featured (KMP feature-flag / configuration library). Brings main up from 1.0.0-Beta1 to the full current architecture (registry redesign #197–#202, plugin moved to repo root #215) plus release prep (#219).

Platform positioning

• Android — Stable (public API covered by SemVer).
• iOS (SKIE/DCE) — Preview, JVM — Preview (public API may change in minor releases without a major bump).

What's in 1.0.0 (since Beta1)

• Per-module featured-manifest.json producer + dev.androidbroadcast.featured.application aggregator → GeneratedFeaturedRegistry.all (Publish per-module Featured manifest (producer side) #197, Add aggregator plugin and GeneratedFeaturedRegistry codegen #198).
• Removed runtime FlagRegistry singleton; FeatureFlagsDebugScreen is now UI-agnostic, takes an explicit registry list (Remove FlagRegistry; make FeatureFlagsDebugScreen UI-agnostic #199).
• Multi-module sample demonstrating the per-feature ConfigValues pattern (Multi-module sample showcasing Featured aggregator plugin #200).
• Restored R8 per-function DCE; synchronous getValueCached / non-suspend is*Enabled() (Restore R8 per-function DCE: sync getValueCached + ProGuard rule fix #201).
• Per-module ConfigValues; generated flag objects are now internal (Per-module ConfigValues + internal generated objects #202).
• Gradle plugin moved from build-logic/ to a repo-root included build (Move Gradle plugin from build-logic/ to repo root #215).
• ConfigValues.observe() catches provider exceptions (Fix ConfigValues.observe to catch provider exceptions #196); user docs migrated to the Wiki (Migrate user documentation to GitHub Wiki #193); ProGuard task renamed to generateFeaturedProguardRules (Rename proguard task to generateFeaturedProguardRules #190).
• Release prep: VERSION_NAME=1.0.0, CHANGELOG [1.0.0], README Platform stability table, corrected false BCV-enforcement claim in CLAUDE.md/CONTRIBUTING.md (Prepare v1.0.0 release #219).

Verification (all green)

• CI on Prepare v1.0.0 release #219 (into develop): Build Android/iOS, Tests & Coverage, Lint, Analyze Kotlin, CodeQL, dependency-review — all pass.
• Local: assemble, test, spotlessCheck, :core:koverVerify (≥90%), plugin tests, publishToMavenLocal, :core:zipXCFramework — all green.
• L5 smoke: Android (Pixel 10) reactive toggle + Debug UI; Compose Desktop launch; iOS FeaturedSampleApp.framework build.

Release mechanics (after merge)

Maven version is derived from the v1.0.0 tag (not gradle.properties). Tagging triggers publish.yml: Central staging (manual promotion), XCFramework GitHub Release, and a bot commit updating Package.swift on main.

Note (known, accepted for this preview iOS release): SPM consumers of v1.0.0 tag will resolve the Beta1 XCFramework (Package.swift is updated by a child commit after the tag). iOS Wiki will document consuming via the release asset / commit pin. SemVer/Android/Maven are unaffected.

Recommended merge method: merge commit (preserve develop history on main, tag the merge commit).

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[cubic-dev-ai]

5 issues found across 144 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="CONTRIBUTING.md">

<violation number="1" location="CONTRIBUTING.md:73">
P2: The Versioning Policy table states all breaking API changes require a MAJOR bump, but the new API Stability section immediately contradicts this by saying iOS/JVM Preview breaking changes can land in MINOR releases. Readers will be confused about which rule to follow — the table has no 'Preview' carve-out.</violation>
</file>

<file name="featured-gradle-plugin/src/main/kotlin/dev/androidbroadcast/featured/gradle/GenerateConfigParamTask.kt">

<violation number="1" location="featured-gradle-plugin/src/main/kotlin/dev/androidbroadcast/featured/gradle/GenerateConfigParamTask.kt:56">
P1: Deleting the entire shared generated directory removes outputs from other tasks (e.g. `FeatureFlagExpect.kt`), making builds order-dependent and potentially failing compilation.</violation>
</file>

<file name="core/src/commonMain/kotlin/dev/androidbroadcast/featured/ConfigValuesExtensions.kt">

<violation number="1" location="core/src/commonMain/kotlin/dev/androidbroadcast/featured/ConfigValuesExtensions.kt:62">
P3: KDoc incorrectly claims `fetch()` warms the snapshot; this can mislead users about when `isEnabled()` reflects fetched values.</violation>
</file>

<file name="core/src/commonMain/kotlin/dev/androidbroadcast/featured/ConfigParam.kt">

<violation number="1" location="core/src/commonMain/kotlin/dev/androidbroadcast/featured/ConfigParam.kt:141">
P2: `enumConstants` is publicly writable for any `ConfigParam<T>`, which allows invalid non-enum metadata and can crash debug UI enum rendering via unchecked `Enum` casts.</violation>
</file>

<file name="core/src/commonTest/kotlin/dev/androidbroadcast/featured/ProviderErrorObserveTest.kt">

<violation number="1" location="core/src/commonTest/kotlin/dev/androidbroadcast/featured/ProviderErrorObserveTest.kt:75">
P2: The test cancels collection in a way that can hide a propagated terminal error, so it may pass even if `observe()` still throws after the second emission.</violation>
</file>

<sub>Note: This PR contains a large number of files. cubic only reviews up to 100 files per PR, so some files may not have been reviewed. cubic prioritizes the most important files to review.
On a pro plan you can use ultrareview for larger PRs.

Re-trigger cubic</sub>

[cubic-dev-ai]

P1: Deleting the entire shared generated directory removes outputs from other tasks (e.g. FeatureFlagExpect.kt), making builds order-dependent and potentially failing compilation.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At featured-gradle-plugin/src/main/kotlin/dev/androidbroadcast/featured/gradle/GenerateConfigParamTask.kt, line 56:

<comment>Deleting the entire shared generated directory removes outputs from other tasks (e.g. `FeatureFlagExpect.kt`), making builds order-dependent and potentially failing compilation.</comment>

<file context>
@@ -48,19 +50,24 @@ public abstract class GenerateConfigParamTask : DefaultTask() {
+        // Clean before writing — the extension file name changed from the fixed
+        // "GeneratedFlagExtensions.kt" to a module-specific name, so stale files
+        // from previous runs must be removed to avoid duplicate-class compile errors.
+        dir.deleteRecursively()
         dir.mkdirs()
 
</file context>

Suggested change

	dir.deleteRecursively()
	dir.listFiles()?.forEach { file ->
	val name = file.name
	if (
	name == "GeneratedFlagExtensions.kt" ||
	name.startsWith("GeneratedLocalFlags") ||
	name.startsWith("GeneratedRemoteFlags") ||
	name.startsWith("GeneratedFlagExtensions")
	) {
	file.delete()
	}
	}

[cubic-dev-ai]

P2: The Versioning Policy table states all breaking API changes require a MAJOR bump, but the new API Stability section immediately contradicts this by saying iOS/JVM Preview breaking changes can land in MINOR releases. Readers will be confused about which rule to follow — the table has no 'Preview' carve-out.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At CONTRIBUTING.md, line 73:

<comment>The Versioning Policy table states all breaking API changes require a MAJOR bump, but the new API Stability section immediately contradicts this by saying iOS/JVM Preview breaking changes can land in MINOR releases. Readers will be confused about which rule to follow — the table has no 'Preview' carve-out.</comment>

<file context>
@@ -63,16 +63,14 @@ Featured follows [Semantic Versioning](https://semver.org/) (`MAJOR.MINOR.PATCH`
 
-Example timeline: deprecated in `1.2.0` → error in `1.3.0` → removed in `2.0.0`.
+- **Android (Stable):** a breaking public-API change (removed/renamed symbol, changed signature) requires a `MAJOR` version bump.
+- **iOS (Preview) and JVM (Preview):** public API may change in `MINOR` releases without a major bump; no migration window is provided.
 
 ## Releasing a New Version
</file context>

[cubic-dev-ai]

P2: enumConstants is publicly writable for any ConfigParam<T>, which allows invalid non-enum metadata and can crash debug UI enum rendering via unchecked Enum casts.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At core/src/commonMain/kotlin/dev/androidbroadcast/featured/ConfigParam.kt, line 141:

<comment>`enumConstants` is publicly writable for any `ConfigParam<T>`, which allows invalid non-enum metadata and can crash debug UI enum rendering via unchecked `Enum` casts.</comment>

<file context>
@@ -131,6 +138,7 @@ public inline fun <reified T : Any> ConfigParam(
     description: String? = null,
     category: String? = null,
     since: String? = null,
+    enumConstants: List<T>? = null,
 ): ConfigParam<T> =
     ConfigParam(
</file context>

[cubic-dev-ai]

P2: The test cancels collection in a way that can hide a propagated terminal error, so it may pass even if observe() still throws after the second emission.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At core/src/commonTest/kotlin/dev/androidbroadcast/featured/ProviderErrorObserveTest.kt, line 75:

<comment>The test cancels collection in a way that can hide a propagated terminal error, so it may pass even if `observe()` still throws after the second emission.</comment>

<file context>
@@ -0,0 +1,90 @@
+                assertEquals(ConfigValue.Source.LOCAL, fromLocal.source)
+                collected.add(fromLocal.value)
+
+                cancelAndIgnoreRemainingEvents()
+            }
+
</file context>

[cubic-dev-ai]

P3: KDoc incorrectly claims fetch() warms the snapshot; this can mislead users about when isEnabled() reflects fetched values.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At core/src/commonMain/kotlin/dev/androidbroadcast/featured/ConfigValuesExtensions.kt, line 62:

<comment>KDoc incorrectly claims `fetch()` warms the snapshot; this can mislead users about when `isEnabled()` reflects fetched values.</comment>

<file context>
@@ -58,8 +58,14 @@ public fun <T : Any> ConfigValues.asStateFlow(
- * This is a convenience wrapper around [ConfigValues.getValue] for [Boolean] parameters,
- * eliminating the need to unwrap the [ConfigValue] envelope at every call site.
+ * This is a **synchronous**, non-suspend read from the in-memory snapshot. It returns
+ * [ConfigParam.defaultValue] before the snapshot is warmed by [ConfigValues.getValue],
+ * [ConfigValues.fetch], or [ConfigValues.override] — matching Firebase Remote Config's
+ * "activate-then-read" contract.
</file context>

Suggested change

	* [ConfigParam.defaultValue] before the snapshot is warmed by [ConfigValues.getValue],
	* [ConfigValues.fetch], or [ConfigValues.override] — matching Firebase Remote Config's
	* [ConfigParam.defaultValue] before the snapshot is warmed by [ConfigValues.getValue]
	* or [ConfigValues.override]. A plain [ConfigValues.fetch] call does not populate the
	* snapshot until a subsequent [ConfigValues.getValue] / [ConfigValues.observe] read occurs.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.