build: apply the AGP 9 config migrations that already work on AGP 8 by AlvaroBrey · Pull Request #3963 · RevenueCat/purchases-android

AlvaroBrey · 2026-08-13T12:27:25Z

Four config changes that AGP 9 requires but that are already valid on AGP 8.13, so they can land ahead of the version bump instead of inflating it:

Library targetSdk moves out of defaultConfig, which AGP 9 removes for libraries, into testOptions.targetSdk and lint.targetSdk.
aarMetadata.minCompileSdk = 1 is now explicit. AGP 9 defaults it to the module's compileSdk, which would silently tighten the published floor from the shipped minCompileSdk=1 to 36.
proguard-android.txt becomes proguard-android-optimize.txt in two internal app modules, since AGP 9 rejects the old file. Not consumer facing.
managedDevices.devices becomes localDevices.
No consumer-visible change and no public API change.

Agent description

Motivation

The AGP 9 upgrade inventory grouped these under "land with the AGP bump", but that grouping is
more conservative than it needs to be. #3945 already landed matchingFallbacks += "defaults" on
AGP 8.13 for the same reason, and the same holds for these four: each is a config shape that AGP 9
requires and AGP 8.13 already accepts.

Splitting them out keeps the eventual AGP 9 PR to genuinely coupled changes. That PR is unusually
large because Gradle 9, AGP 9, Kotlin 2.3 and Poko cannot be separated from each other, so anything
that can be removed from it is worth removing.

Description

targetSdk: for a library module it only ever fed instrumentation tests and lint. AGP 9 drops
it from defaultConfig, and both consumers now take it directly, so it moves to
testOptions.targetSdk and lint.targetSdk in ConfigureAndroidLibrary.kt.
aarMetadata.minCompileSdk = 1: AGP 8 defaults this to 1, so setting it explicitly is a no-op
today. Under AGP 9 the default becomes the module's compileSdk, so leaving it implicit would
raise the floor consumers must compile against from 1 to 36. Pinning it now means the AGP bump
cannot change the published contract by accident.
proguard: getDefaultProguardFile("proguard-android.txt") to the -optimize variant in
integration-tests and examples/purchase-tester. AGP 9 rejects the non-optimize file.
managed devices: testOptions.managedDevices.devices is deprecated in favor of localDevices.
localDevices is a NamedDomainObjectContainer<ManagedVirtualDevice> rather than a polymorphic
container, so create<ManagedVirtualDevice>("pixel6Api34") fails with
Container 'ManagedVirtualDevice container' is not polymorphic. The type argument and the now
unused import are removed.

Not needed, contrary to the inventory

The inventory flagged :feature:admob as possibly needing its own matchingFallbacks += "defaults",
alongside :feature:amazon and :feature:galaxy. It does not. matchingFallbacks is declared once
on the customEntitlementComputation application flavor in
ConfigureApisFlavorsForApplication.kt, not per library, so all three defaults-only feature modules
are already covered by the change that shipped in #3945.

Testing

Everything below on the current AGP 8.13.2 and Gradle 8.14.5, since the point is that these do not
need AGP 9:

assembleDebug across all modules, plus :integration-tests:assembleDebug and
:examples:purchase-tester:assembleDebug for the proguard change specifically.
detektAll.
scripts/api-check.sh with no signature diff.
Unpacked the release AAR and confirmed aar-metadata.properties still contains minCompileSdk=1,
which is the regression this change exists to prevent.

Note

Low Risk
Build and tooling-only changes with no public API impact; integration-test ProGuard tweaks affect an internal minified test app only.

Overview
Prepares the repo for AGP 9 by landing config shape changes that are already valid on AGP 8.13, so they do not need to ride with the larger version bump.

In shared library convention (ConfigureAndroidLibrary.kt), targetSdk is removed from defaultConfig and set on testOptions.targetSdk and lint.targetSdk, matching AGP 9’s library model. aarMetadata.minCompileSdk = 1 is set explicitly so AGP 9 cannot default it to compileSdk and raise the published compile floor.

integration-tests and examples/purchase-tester switch release minification to proguard-android-optimize.txt (AGP 9 rejects the old default). For integration tests, ProGuard keeps kotlin.** and androidx.tracing.** so R8 optimization does not strip classes the androidTest APK still needs at runtime.

baselineprofile uses testOptions.managedDevices.localDevices instead of deprecated devices, with a non-polymorphic create("pixel6Api34") call.

^{Reviewed by Cursor Bugbot for commit 0d4e50c. Bugbot is set up for automated code reviews on this repo. Configure here.}

tonidero

Thanks for iterating on this! I think it makes sense!

codecov · 2026-08-13T15:05:49Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.68%. Comparing base (4d97e6e) to head (0d4e50c).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3963   +/-   ##
=======================================
  Coverage   82.68%   82.68%           
=======================================
  Files         425      425           
  Lines       17475    17475           
  Branches     2629     2629           
=======================================
  Hits        14450    14450           
  Misses       2138     2138           
  Partials      887      887

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

AlvaroBrey · 2026-08-13T15:32:28Z

This stack of pull requests is managed by Graphite. Learn more about stacking.

Each of these is required by AGP 9 but valid today, so they can land ahead of the version bump instead of inflating it: - library targetSdk moves out of defaultConfig, where AGP 9 removes it, into testOptions.targetSdk and lint.targetSdk, the only two things it ever affected for a library - aarMetadata.minCompileSdk pinned to 1. AGP 9 would otherwise default it to the module compileSdk and tighten the published floor to 36 - proguard-android-optimize.txt replaces proguard-android.txt, which AGP 9 rejects - managedDevices.devices becomes localDevices matchingFallbacks is already handled once on the application flavor, so the defaults-only feature modules need nothing per-module.

AGP 9 removes proguard-android.txt, whose only meaningful difference from proguard-android-optimize.txt is -dontoptimize, so switching enabled R8 optimization on this module for the first time. The app and androidTest APKs are minified separately but share one classloader, and the test APK links against runtime classes that ship in the app APK. Optimization prunes whatever the app itself stops referencing, so instrumentation died before running anything. Observed in sequence on device, each masking the next: NoSuchMethodError kotlin.jvm.internal.Intrinsics.checkNotNullParameter NoClassDefFound androidx.tracing.Trace NoClassDefFound kotlin.LazyKt Keeping the Kotlin runtime and androidx.tracing fixes it at the root rather than switching optimization back off: the test class scanner now reports numtests=2, matching the pre-AGP-9 run, and the tests execute.

> [!NOTE] > This targets branch `11.0-dev` which will become the epic branch for the upcoming major release. Once this first PR is merged, I'll open a continuous one from that one to `main` until we are ready to release it altogether. - Moves the SDK's build toolchain to AGP 9: | Dependency | From | To | |---|---|---| | AGP | 8.13.2 | **9.2.1** | | Gradle | 8.14.5 | **9.4.1** | | Kotlin | 2.0.21 | **2.2.21** | | Poko | 0.17.2 | **0.20.2** | | Paparazzi | 2.0.0-alpha02 | **2.0.0-alpha05** | - No public API change and no `api*.txt` diff. - **Why this becomes a major**: this transitively raises the miminum kotlin version for consumers to 2.1.0. up from 1.8.0. - Kotlin lands on **2.2.21, the minimum required by AGP 9**, - AGP is capped at **9.2.1** rather than latest: AGP 9.3.x requires Gradle 9.5+, and Gradle 9.5+ embeds a Kotlin that a 2.2 compiler cannot read, bumping consumers to an even higher minimum Kotlin version. - Nothing downstream needs AGP 9 or Gradle 9, just the Kotlin bump. The published AAR metadata is unchanged (`minCompileSdk=1`, `minAndroidGradlePluginVersion=1.0.0`). Companion docs PR: RevenueCat/docs#1942 Companion PHC PR: RevenueCat/purchases-hybrid-common#1844 ### Checklist - [ ] If applicable, unit tests - [ ] If applicable, create follow-up issues for `purchases-ios` and hybrids <details><summary>Agent description</summary> ### Motivation AGP 8 is increasingly behind, and AGP 9 removes a number of DSL surfaces we still used. The prerequisite work already landed separately in #3931, #3961 and #3963. AGP 9 has a runtime dependency on Kotlin Gradle Plugin **2.2.10 or higher**, so a Kotlin bump is not optional here. Everything above that floor is a choice, and this PR deliberately takes the minimum. ### Why not Kotlin 2.3.x An earlier revision of this branch used Kotlin 2.3.21. Measuring the cost changed the decision: - **It breaks every React Native consumer.** We publish `kotlin-stdlib` at `compile` scope and Gradle resolves consumers onto it. A compiler reads metadata at most one minor ahead. Kotlin 2.3.x publishes metadata 2.3.0, and React Native's own Gradle plugin pins the compiler: 2.0.21 through RN 0.79, 2.1.20 through RN 0.86, with only RN `main` on 2.2.0. Reproduced on a real RN 0.86 app: `metadata version is 2.3.0 / compiler version 2.1.0 can read versions up to 2.2.0`. Every RN app would have needed an explicit `kotlin-gradle-plugin` version in `android/build.gradle`. - **It forces the K2 migration.** Kotlin 2.3.21 rejects `languageVersion 1.8` outright. 2.2.x still accepts it, so the frontend migration stays out of a version bump where it does not belong. - **It does not avoid a second bump anyway.** Kotlin 2.4 removes `languageVersion 1.8` regardless. At Kotlin 2.2.21 the published metadata is 2.2.0, which RN 0.81+ reads untouched. ### Why AGP 9.2.1 and Gradle 9.4.1 This is the non-obvious constraint, and CI found it rather than local builds. `:codegen` is a `java-gradle-plugin` module, so it compiles against the Kotlin that **Gradle itself embeds**. Embedded Kotlin by Gradle release: | Gradle | Embedded Kotlin | Readable by a 2.2 compiler (max 2.3.0) | |---|---|---| | 9.3.1 | 2.2.21 | yes | | 9.4.1 | 2.3.0 | yes, exactly at the limit | | 9.5.1 | 2.3.20 | no | | 9.7.0 | 2.4.0 | no | Gradle 9.7.0 therefore failed `prepare-tests` with `metadata version is 2.4.0, but the compiler version 2.2.0 can read versions up to 2.3.0`. AGP 9.3.x requires Gradle 9.5.0 or higher (`Minimum supported Gradle version is 9.5.0`), which is exactly the range we cannot read. **AGP 9.2.1 is the newest release that runs on Gradle 9.4.1**; 9.1.1 and 9.0.1 were also confirmed to work, 9.3.1 was confirmed not to. So the AGP ceiling here is a consequence of the Kotlin floor, not an independent preference. When the deferred Kotlin 2.3 bump happens, AGP and Gradle can move up with it. ### Also in this PR - Standalone sample apps (`CustomEntitlementComputationSample`, `MagicWeather`, `MagicWeatherCompose`) move to Kotlin 2.2.21 and gain the `compose-compiler` plugin alias. They consume our published artifacts, so they need a compiler that can read our metadata. - Unit tests are re-enabled on the release variant via `HasUnitTestBuilder.enableUnitTest`, because AGP 9 only creates unit tests for the `testBuildType` variant and the published variant is release. - The `androidDependencies` cache-warm CI step is dropped; AGP 9 removed that task. - `migrations/v11-MIGRATION.md` documents the new Kotlin floor, mirroring the v9 guide. - README `Requirements` now says Kotlin 2.1.0+. ### Deferred on purpose - **Kotlin 2.3 and the K1 to K2 migration**, until React Native ships the KGP 2.2 pin already on its `main` branch. Doing it sooner buys nothing and costs every RN app a migration step. - **AGP 9 built-in Kotlin** (previously #3965). Not breaking and not required; the `android.builtInKotlin=false` / `android.newDsl=false` opt-out only has to go at AGP 10. ### Testing - `assembleDebug` across all modules; release AARs for `:purchases` and `:ui:revenuecatui`. - `:purchases` unit tests, `:ui:debugview:verifyPaparazziDefaultsDebug`, `detektAll`. - `scripts/api-check.sh` with **zero** `api*.txt` diff. - Published contract checked directly: POM carries `kotlin-stdlib:2.2.21` at `compile` scope, the release AAR still reports `minCompileSdk=1` and `minAndroidGradlePluginVersion=1.0.0`, and our own classes carry metadata `mv = {1, 8, 0}`. - Consumer floor measured against the real release AAR plus the stdlib we publish: Kotlin 2.1.21 compiles; 2.0.21 and 1.9.24 fail. That is what the 2.1.0 claim in the README rests on. ### Downstream The Kotlin floor is what propagates, not AGP. Nothing downstream needs AGP 9 or Gradle 9. The only direct consumer is purchases-hybrid-common, which re-exposes us at compile scope via `api(libs.purchases)`. RevenueCat/purchases-hybrid-common#1844 raises its Kotlin accordingly, and the hybrid SDKs pick the floor up from there rather than from this repo. Documentation follows separately: - RevenueCat/docs#1942 adds the Kotlin minimum to the Android, Flutter and React Native installation pages, and adds the 9.x-to-10.x and 10.x-to-11.x migration guides the site was missing. - RevenueCat/purchases-flutter#1876 states the Kotlin minimum in that repo's README. Flutter applies the version from the app's `android/settings.gradle`, so the requirement lands on the consuming app and the Flutter version itself does not move. - RevenueCat/react-native-purchases#1925 raises the React Native floor to 0.80.0, the first release whose Gradle plugin pins a Kotlin that can read our metadata. </details>  --- > [!NOTE] > **Medium Risk** > Major toolchain and minimum Kotlin version changes affect all consumers and CI, though public API and published AAR AGP/minSdk metadata are intentionally unchanged. > > **Overview** > This PR moves the SDK build to **AGP 9.2.1**, **Gradle 9.4.1**, and **Kotlin 2.2.21**, and bumps related tooling (Poko, Paparazzi, baseline profile plugin). **`gradle.properties`** opts out of AGP 9’s built-in Kotlin and new DSL for now. > > The **consumer-facing change** is a higher Kotlin floor: README and **`migrations/v11-MIGRATION.md`** document **Kotlin 2.1.0+** (up from 1.8.0), driven by published stdlib metadata—not a public API change. > > **Build-logic** re-enables unit tests on library variants under AGP 9 via **`enableUnitTest`**, and keeps **`aarMetadata.minCompileSdk = 1`** so published AAR requirements don’t tighten. > > Compose sample apps switch to the **Kotlin Compose compiler plugin** and drop **`composeOptions.kotlinCompilerExtensionVersion`**. Several modules replace deprecated **`kotlinOptions`** with **`kotlin.compilerOptions.jvmTarget`**. > > **CircleCI** drops the removed **`androidDependencies`** warmup and uses Gradle cache restore on standalone sample builds instead. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 1b6b4df. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup>

> [!NOTE] > This targets branch `11.0-dev` which will become the epic branch for the upcoming major release. Once this first PR is merged, I'll open a continuous one from that one to `main` until we are ready to release it altogether. - Moves the SDK's build toolchain to AGP 9: | Dependency | From | To | |---|---|---| | AGP | 8.13.2 | **9.2.1** | | Gradle | 8.14.5 | **9.4.1** | | Kotlin | 2.0.21 | **2.2.21** | | Poko | 0.17.2 | **0.20.2** | | Paparazzi | 2.0.0-alpha02 | **2.0.0-alpha05** | - No public API change and no `api*.txt` diff. - **Why this becomes a major**: this transitively raises the miminum kotlin version for consumers to 2.1.0. up from 1.8.0. - Kotlin lands on **2.2.21, the minimum required by AGP 9**, - AGP is capped at **9.2.1** rather than latest: AGP 9.3.x requires Gradle 9.5+, and Gradle 9.5+ embeds a Kotlin that a 2.2 compiler cannot read, bumping consumers to an even higher minimum Kotlin version. - Nothing downstream needs AGP 9 or Gradle 9, just the Kotlin bump. The published AAR metadata is unchanged (`minCompileSdk=1`, `minAndroidGradlePluginVersion=1.0.0`). Companion docs PR: RevenueCat/docs#1942 Companion PHC PR: RevenueCat/purchases-hybrid-common#1844 - [ ] If applicable, unit tests - [ ] If applicable, create follow-up issues for `purchases-ios` and hybrids <details><summary>Agent description</summary> AGP 8 is increasingly behind, and AGP 9 removes a number of DSL surfaces we still used. The prerequisite work already landed separately in #3931, #3961 and #3963. AGP 9 has a runtime dependency on Kotlin Gradle Plugin **2.2.10 or higher**, so a Kotlin bump is not optional here. Everything above that floor is a choice, and this PR deliberately takes the minimum. An earlier revision of this branch used Kotlin 2.3.21. Measuring the cost changed the decision: - **It breaks every React Native consumer.** We publish `kotlin-stdlib` at `compile` scope and Gradle resolves consumers onto it. A compiler reads metadata at most one minor ahead. Kotlin 2.3.x publishes metadata 2.3.0, and React Native's own Gradle plugin pins the compiler: 2.0.21 through RN 0.79, 2.1.20 through RN 0.86, with only RN `main` on 2.2.0. Reproduced on a real RN 0.86 app: `metadata version is 2.3.0 / compiler version 2.1.0 can read versions up to 2.2.0`. Every RN app would have needed an explicit `kotlin-gradle-plugin` version in `android/build.gradle`. - **It forces the K2 migration.** Kotlin 2.3.21 rejects `languageVersion 1.8` outright. 2.2.x still accepts it, so the frontend migration stays out of a version bump where it does not belong. - **It does not avoid a second bump anyway.** Kotlin 2.4 removes `languageVersion 1.8` regardless. At Kotlin 2.2.21 the published metadata is 2.2.0, which RN 0.81+ reads untouched. This is the non-obvious constraint, and CI found it rather than local builds. `:codegen` is a `java-gradle-plugin` module, so it compiles against the Kotlin that **Gradle itself embeds**. Embedded Kotlin by Gradle release: | Gradle | Embedded Kotlin | Readable by a 2.2 compiler (max 2.3.0) | |---|---|---| | 9.3.1 | 2.2.21 | yes | | 9.4.1 | 2.3.0 | yes, exactly at the limit | | 9.5.1 | 2.3.20 | no | | 9.7.0 | 2.4.0 | no | Gradle 9.7.0 therefore failed `prepare-tests` with `metadata version is 2.4.0, but the compiler version 2.2.0 can read versions up to 2.3.0`. AGP 9.3.x requires Gradle 9.5.0 or higher (`Minimum supported Gradle version is 9.5.0`), which is exactly the range we cannot read. **AGP 9.2.1 is the newest release that runs on Gradle 9.4.1**; 9.1.1 and 9.0.1 were also confirmed to work, 9.3.1 was confirmed not to. So the AGP ceiling here is a consequence of the Kotlin floor, not an independent preference. When the deferred Kotlin 2.3 bump happens, AGP and Gradle can move up with it. - Standalone sample apps (`CustomEntitlementComputationSample`, `MagicWeather`, `MagicWeatherCompose`) move to Kotlin 2.2.21 and gain the `compose-compiler` plugin alias. They consume our published artifacts, so they need a compiler that can read our metadata. - Unit tests are re-enabled on the release variant via `HasUnitTestBuilder.enableUnitTest`, because AGP 9 only creates unit tests for the `testBuildType` variant and the published variant is release. - The `androidDependencies` cache-warm CI step is dropped; AGP 9 removed that task. - `migrations/v11-MIGRATION.md` documents the new Kotlin floor, mirroring the v9 guide. - README `Requirements` now says Kotlin 2.1.0+. - **Kotlin 2.3 and the K1 to K2 migration**, until React Native ships the KGP 2.2 pin already on its `main` branch. Doing it sooner buys nothing and costs every RN app a migration step. - **AGP 9 built-in Kotlin** (previously #3965). Not breaking and not required; the `android.builtInKotlin=false` / `android.newDsl=false` opt-out only has to go at AGP 10. - `assembleDebug` across all modules; release AARs for `:purchases` and `:ui:revenuecatui`. - `:purchases` unit tests, `:ui:debugview:verifyPaparazziDefaultsDebug`, `detektAll`. - `scripts/api-check.sh` with **zero** `api*.txt` diff. - Published contract checked directly: POM carries `kotlin-stdlib:2.2.21` at `compile` scope, the release AAR still reports `minCompileSdk=1` and `minAndroidGradlePluginVersion=1.0.0`, and our own classes carry metadata `mv = {1, 8, 0}`. - Consumer floor measured against the real release AAR plus the stdlib we publish: Kotlin 2.1.21 compiles; 2.0.21 and 1.9.24 fail. That is what the 2.1.0 claim in the README rests on. The Kotlin floor is what propagates, not AGP. Nothing downstream needs AGP 9 or Gradle 9. The only direct consumer is purchases-hybrid-common, which re-exposes us at compile scope via `api(libs.purchases)`. RevenueCat/purchases-hybrid-common#1844 raises its Kotlin accordingly, and the hybrid SDKs pick the floor up from there rather than from this repo. Documentation follows separately: - RevenueCat/docs#1942 adds the Kotlin minimum to the Android, Flutter and React Native installation pages, and adds the 9.x-to-10.x and 10.x-to-11.x migration guides the site was missing. - RevenueCat/purchases-flutter#1876 states the Kotlin minimum in that repo's README. Flutter applies the version from the app's `android/settings.gradle`, so the requirement lands on the consuming app and the Flutter version itself does not move. - RevenueCat/react-native-purchases#1925 raises the React Native floor to 0.80.0, the first release whose Gradle plugin pins a Kotlin that can read our metadata. </details>  --- > [!NOTE] > **Medium Risk** > Major toolchain and minimum Kotlin version changes affect all consumers and CI, though public API and published AAR AGP/minSdk metadata are intentionally unchanged. > > **Overview** > This PR moves the SDK build to **AGP 9.2.1**, **Gradle 9.4.1**, and **Kotlin 2.2.21**, and bumps related tooling (Poko, Paparazzi, baseline profile plugin). **`gradle.properties`** opts out of AGP 9’s built-in Kotlin and new DSL for now. > > The **consumer-facing change** is a higher Kotlin floor: README and **`migrations/v11-MIGRATION.md`** document **Kotlin 2.1.0+** (up from 1.8.0), driven by published stdlib metadata—not a public API change. > > **Build-logic** re-enables unit tests on library variants under AGP 9 via **`enableUnitTest`**, and keeps **`aarMetadata.minCompileSdk = 1`** so published AAR requirements don’t tighten. > > Compose sample apps switch to the **Kotlin Compose compiler plugin** and drop **`composeOptions.kotlinCompilerExtensionVersion`**. Several modules replace deprecated **`kotlinOptions`** with **`kotlin.compilerOptions.jvmTarget`**. > > **CircleCI** drops the removed **`androidDependencies`** warmup and uses Gradle cache restore on standalone sample builds instead. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 1b6b4df. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup>

AlvaroBrey added the pr:other label Aug 13, 2026

AlvaroBrey self-assigned this Aug 13, 2026

AlvaroBrey force-pushed the build/agp9-prep branch from b25588b to e1b8e81 Compare August 13, 2026 12:42

AlvaroBrey marked this pull request as ready for review August 13, 2026 12:42

AlvaroBrey requested a review from a team as a code owner August 13, 2026 12:43

AlvaroBrey force-pushed the build/agp9-prep branch from e1b8e81 to 42db9cb Compare August 13, 2026 12:57

AlvaroBrey changed the base branch from main to fix/expose-compose-foundation-layout August 13, 2026 12:57

AlvaroBrey force-pushed the build/agp9-prep branch from 42db9cb to e717b61 Compare August 13, 2026 13:06

AlvaroBrey changed the base branch from fix/expose-compose-foundation-layout to build/relocate-baseline-profiles August 13, 2026 13:06

AlvaroBrey force-pushed the build/agp9-prep branch from aeade6c to a6be389 Compare August 13, 2026 14:48

tonidero reviewed Aug 13, 2026

View reviewed changes

Comment thread ...ain/kotlin/com/revenuecat/purchases/android/buildlogic/convention/ConfigureAndroidLibrary.kt

tonidero approved these changes Aug 13, 2026

View reviewed changes

AlvaroBrey force-pushed the build/agp9-prep branch from a6be389 to 9bd81de Compare August 13, 2026 19:22

AlvaroBrey force-pushed the build/relocate-baseline-profiles branch from 04770f0 to 43609fc Compare August 13, 2026 19:22

Base automatically changed from build/relocate-baseline-profiles to main August 13, 2026 19:55

AlvaroBrey added 2 commits August 13, 2026 21:56

AlvaroBrey force-pushed the build/agp9-prep branch from 9bd81de to 0d4e50c Compare August 13, 2026 19:56

AlvaroBrey enabled auto-merge August 13, 2026 19:57

AlvaroBrey added this pull request to the merge queue Aug 13, 2026

Merged via the queue into main with commit b2d7cf2 Aug 13, 2026
37 checks passed

AlvaroBrey deleted the build/agp9-prep branch August 13, 2026 20:32

RCGitBot mentioned this pull request Aug 18, 2026

[AUTOMATIC] Release/10.17.0 #3993

Merged

Navigation Menu

Uh oh!

build: apply the AGP 9 config migrations that already work on AGP 8 - #3963

build: apply the AGP 9 config migrations that already work on AGP 8#3963
AlvaroBrey merged 2 commits into
mainfrom
build/agp9-prep

AlvaroBrey commented Aug 13, 2026 •

edited by cursor Bot

Loading

Uh oh!

tonidero left a comment

Uh oh!

Uh oh!

codecov Bot commented Aug 13, 2026 •

edited

Loading

Uh oh!

AlvaroBrey commented Aug 13, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

AlvaroBrey commented Aug 13, 2026 • edited by cursor Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Motivation

Description

Not needed, contrary to the inventory

Testing

Uh oh!

tonidero left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

codecov Bot commented Aug 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

AlvaroBrey commented Aug 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

AlvaroBrey commented Aug 13, 2026 •

edited by cursor Bot

Loading

codecov Bot commented Aug 13, 2026 •

edited

Loading

AlvaroBrey commented Aug 13, 2026 •

edited

Loading