4.0.2

Startup 4.0.2 fixes nested manifest installation, improves failure diagnostics, and avoids CPU spinning while Kotlin/Native threads wait for initialization. Public Kotlin and Swift APIs and platform requirements are unchanged.

Fixes

• An initializer can install another manifest from inside create without a false cycle error.
• A StartupException thrown by create without component information now identifies the failing initializer and retains the original exception as its cause.
• Kotlin/Native threads waiting for the startup lock now block on a recursive pthread mutex instead of spinning.
• The sample framework uses supported Gradle dependency notation, and wrapper line endings are pinned for each platform.

Upgrade note

Each non-Android install now starts the eager components in the supplied manifest and their dependencies, matching Android. Installing an unrelated manifest no longer retries eager components left uncreated by an earlier failed install. Retry by installing the original or corrected manifest, or by requesting the component explicitly.

implementation("io.github.kunal26das:startup:4.0.2")

For Swift, update both api(...) and framework export(...) to 4.0.2. See the migration guide and changelog.