v0.3.0

No functional changes to composure-core, composure-compose, or composure-ios since 0.1.0. This version exists because 0.1.0 is already published to Maven Central, which doesn't allow re-publishing the same version, but never completed its GitHub Release or Swift Package Manager release due to the pipeline issues below.

v0.2.0

No functional changes to composure-core, composure-compose, or composure-ios since 0.1.0. This version exists because 0.1.0 is already published to Maven Central, which doesn't allow re-publishing the same version, but never completed its GitHub Release or Swift Package Manager release due to the pipeline issues below.

Fixed

• Release pipeline (release.yml): the Maven Central publish step now runs with --no-configuration-cache, since publishToMavenCentral isn't compatible with Gradle's configuration cache yet.
• Release pipeline: the GitHub Release step is now idempotent, so retrying a tag after an earlier failed attempt no longer errors with "a release with the same tag name already exists".

v0.1.0: fix: disable configuration cache for the Maven Central publish step

publishToMavenCentral fails under configuration caching — Gradle's
PublishToMavenRepository task isn't compatible with it yet
(gradle/gradle#22779). gradle.properties enables config cache globally,
so this step needs --no-configuration-cache to opt back out.