Skip to content

Release 1.1.1: bump library versions and modernize release workflow - #131

Merged
Vacxe merged 3 commits into
masterfrom
release-1.1.1
Sep 3, 2026
Merged

Release 1.1.1: bump library versions and modernize release workflow#131
Vacxe merged 3 commits into
masterfrom
release-1.1.1

Conversation

@Vacxe

@Vacxe Vacxe commented Sep 3, 2026

Copy link
Copy Markdown
Member

What changed

  • Library versions bumped to 1.1.1 for compose, compose-ui, compose-test and compose-semantics in gradle.properties. This is the first release after the toolchain upgrade merged in bump versions #130 (Gradle 9.7.1, AGP 9.4.0, Kotlin 2.4.10, Compose 1.12.0).
  • Release workflow modernized. publish-release-workflow.yaml moves from actions/checkout@v1 and actions/setup-java@v1 to the @v4 versions with an explicit Temurin 17 distribution and Gradle caching, matching what the snapshot workflow already uses. The unused little-core-labs/get-git-tag step (Node 12, output never read) is removed.
  • New manual "Publish All Libraries Release" workflow (publish-release-all.yml). Triggered from the Actions tab via workflow_dispatch, it fans the shared release workflow out to all four libraries as parallel matrix jobs with fail-fast: false, so one failure does not cancel the others. The existing per-library tag triggers are unchanged.
  • IDE project files regenerated by Android Studio after the Gradle 9 sync.

Why

  • 1.1.0 is already published on Maven Central for all four artifacts, so a release from the current version would be rejected as a duplicate.
  • The release workflow has never run in CI. Its @v1 actions run on the retired Node 12 runtime and fetch JDKs from an old Zulu CDN listing, so the first tag-triggered release would most likely have failed at setup.
  • Releasing all four libraries previously required pushing four separate tags.

Reviewer notes

  • Breaking change for consumers. The upstream Compose 1.12 / AndroidX bumps forced minSdk from 21 to 23 and the JVM target from 8 to 11. Those changes landed in bump versions #130; this PR only assigns the version. Consider a changelog note about the new minimum API level.
  • The manual workflow only appears in the Actions tab once this PR is merged to master, since workflow_dispatch entries are read from the default branch. Run it from master after merging.
  • After the Gradle upload, each deployment still needs to be published manually in the Sonatype Central Portal. Nothing in this PR changes that.
  • No YAML linter was available locally; the workflow edits were verified by inspection.

🤖 Generated with Claude Code

- lib.version.* -> 1.1.1 for compose, compose-ui, compose-test, compose-semantics
- publish-release-workflow: actions/checkout@v4, actions/setup-java@v4 (Temurin 17) with Gradle cache
Android Studio regenerated these on sync after the toolchain upgrade.
publish-release-all.yml is triggered via workflow_dispatch and fans the shared
release workflow out to compose, compose-semantics, compose-test and compose-ui
as parallel matrix jobs with fail-fast disabled.

Also drop the unused little-core-labs/get-git-tag step from the shared workflow:
nothing reads its output and it runs on the retired Node 12 runtime.
@Vacxe
Vacxe enabled auto-merge September 3, 2026 09:22
@Vacxe
Vacxe merged commit fa6c022 into master Sep 3, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant