Skip to content

ci(replay): Test Session Replay against Compose UI versions from a checked-in file - #6638

Draft
sentry-junior[bot] wants to merge 4 commits into
mainfrom
ci/compose-ui-matrix
Draft

sentry-junior[bot] wants to merge 4 commits into
mainfrom
ci/compose-ui-matrix

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

📜 Description

This replaces the hardcoded composeUiTestVersions build types from #6626 (composeUi112, composeUi113) with a Compose UI matrix that follows the Spring Boot matrix pattern:

  • gradle/compose-ui-versions.json lists the Compose UI versions to test: the latest stable and, if it's newer, the latest pre-release.
  • A new build-logic plugin, io.sentry.dependency-matrix, reads a versions file from gradle/ and registers a <name>Test<version> task for each version, such as composeUiTest1_13_0_rc01. Each task runs the module's unit tests with every dependency in the given group at that version:
    dependencyMatrix {
      matrix(name = "composeUi", group = "androidx.compose.ui", versionsFile = "compose-ui-versions.json")
    }
    • Android modules: one build type per version, based on the test build type. Each version needs its own variant, because AGP builds the R class and test resources from the variant's dependencies. The matrix unit tests are kept out of test/check, so the required Build Job only runs the release unit tests.
    • JVM modules (e.g. a future okhttp matrix): the compiled tests run on a versioned runtime classpath, like SpringBootMatrixPlugin.
  • .github/workflows/compose-ui-matrix.yml reads the file inline with jq like the Spring Boot workflows, and runs one job per version on PRs and on pushes to main.

The same commit always tests the same versions. A new Compose release comes in as a change to the JSON file.

💡 Motivation and Context

Session Replay calls Compose internals whose mangled JVM names change between Compose versions. Adding or removing a version is now a one-line change to the JSON file, and other dependencies (Room, okhttp, ...) can reuse the plugin.

Trade-off: check still compiles the matrix variants, because verifyMethodParameters reads every variant's AAR. That's the same as on main today.

📝 Checklist

  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

Once this merges, a daily Junior automation bumps gradle/compose-ui-versions.json when Google Maven has a newer Compose UI version. It force-pushes chore/update-jetpack-compose-ui-tests and asks @getsentry/team-mobile-android-sdk to review. Dependabot can't update a custom JSON file, and getsentry/github-workflows/updater only follows git tags, which AndroidX doesn't publish for Compose.

#skip-changelog

via roman.

--

View Session [Sentry]

…s from Google Maven

Replace the hardcoded composeUi112/composeUi113 build types with a
Compose UI matrix workflow. Like the AGP matrix in
sentry-android-gradle-plugin, a Kotlin script reads
androidx.compose.ui:ui's maven-metadata.xml and picks the latest stable
and, when newer, the latest pre-release. Each matrix job runs the replay
unit tests with VERSION_COMPOSE_UI forcing that version on the test
runtime classpath. The workflow also runs daily, so new Compose releases
are tested without a version bump PR.

Co-Authored-By: Roman Zavarnitsyn <roman.zavarnitsyn@sentry.io>
@sentry

sentry Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

📲 Install Builds

Android

🔗 App Name App ID Version Configuration
SDK Size io.sentry.tests.size 8.65.0 (1) release

⚙️ sentry-android Build Distribution Settings

sentry-junior Bot and others added 2 commits November 17, 2026 11:32
GitHub only notifies the workflow's creator about scheduled runs, which
is the bot that pushed it, so a failing daily run would go unnoticed.
On a scheduled failure, open an issue, or comment on the open one so
repeated failures stay in one place.

Co-Authored-By: Roman Zavarnitsyn <roman.zavarnitsyn@sentry.io>
Like the Spring Boot matrix, keep the Compose UI versions in
gradle/compose-ui-versions.json instead of looking them up on Google
Maven on every run, so the same commit always tests the same versions.
Drop the daily schedule and its failure issue, which only made sense
with the live lookup.

Co-Authored-By: Roman Zavarnitsyn <roman.zavarnitsyn@sentry.io>
@sentry-junior sentry-junior Bot changed the title ci(replay): Test Session Replay against the latest Compose UI versions from Google Maven ci(replay): Test Session Replay against Compose UI versions from a checked-in file Nov 17, 2026
…ency matrix plugin

Adds io.sentry.dependency-matrix, which reads a versions file in gradle/ and
registers <name>Test<version> tasks. Android modules get a build type per
version, kept out of check; JVM modules reuse the compiled tests on a
versioned runtime classpath. The workflow reads the file with jq inline,
like the Spring Boot matrix workflows.

Co-Authored-By: roman <roman.zavarnitsyn@sentry.io>
Co-Authored-By: Nelson Osacky <nelson.osacky@sentry.io>

This branch has not been deployed

No deployments
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.

0 participants