0.2.1-to-0.2.2.md

icon	lucide/arrow-right-left

Migrating from 0.2.1 to 0.2.2

Version 0.2.2 changes how you depend on Some.

If you are upgrading from 0.2.1, the main change is the artifact split:

• dev.appoutlet:some becomes dev.appoutlet:some-core for JVM projects
• dev.appoutlet:some-android is the Android artifact

What changed in 0.2.2

In 0.2.1, projects used a single artifact:

testImplementation("dev.appoutlet:some:0.2.1")

In 0.2.2, Some is published as separate artifacts:

• JVM: dev.appoutlet:some-core:0.2.2
• Android: dev.appoutlet:some-android:0.2.2

This is a dependency change, not a Kotlin API change.

What did not change

• The package name is still dev.appoutlet.some
• You still call some<T>() and someSetup {}
• Existing configuration and fixture generation APIs remain the same
• Your existing imports for the shared API do not need to change

JVM users

Replace the old JVM dependency with some-core.

Before:

testImplementation("dev.appoutlet:some:0.2.1")

After:

testImplementation("dev.appoutlet:some-core:0.2.2")

No source changes are required if you were already using some<T>() or someSetup {}.

Android users

If your Android tests were using the old some artifact, switch to some-android.

Before:

testImplementation("dev.appoutlet:some:0.2.1")

After:

testImplementation("dev.appoutlet:some-android:0.2.2")

some-android re-exports the core API, so you should not add some-core separately.

Summary

• JVM users: replace some with some-core
• Android users: replace some with some-android
• Keep the same package, imports, and shared Kotlin API