From 9689dd41c0716d4606ffa9dc55940078b87780bb Mon Sep 17 00:00:00 2001 From: Will Griffin Date: Wed, 5 Aug 2026 13:03:33 -0600 Subject: [PATCH] fix(deps): stop Renovate bumping androidx past the compileSdk 36 pin androidx.core 1.18+ and androidx.lifecycle 2.11+ require compileSdk 37, and both seed apps are pinned to compileSdk 36. The catalogs recorded that coupling only in comments, which Renovate cannot read, so every weekly update bumped core-ktx and lifecycle straight past it and left :sample:checkDebugAarMetadata failing the whole PR. Encode the constraint as two allowedVersions rules so the pin survives the weekly run, matching how renovate.json already expresses the template-package pin. Closes #2234 --- renovate.json | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/renovate.json b/renovate.json index a8b2c7a739..2b0668c2bf 100644 --- a/renovate.json +++ b/renovate.json @@ -7,6 +7,18 @@ "matchFileNames": ["packages/*/template/package.json"], "matchPackageNames": ["@happyvertical/smrt-*"], "enabled": false + }, + { + "description": "androidx.core 1.18+ and androidx.lifecycle 2.11+ require compileSdk 37, and both seed apps are pinned to compileSdk 36 (packages/smrt-android/AGENTS.md, and android-compile-sdk in each gradle/libs.versions.toml). The catalogs record that coupling in comments, which Renovate cannot read, so every weekly update bumped straight past it and left :sample:checkDebugAarMetadata failing on the whole PR (#2234). Remove these two rules in the same change that moves the toolchain to compileSdk 37.", + "matchManagers": ["gradle"], + "matchPackageNames": ["androidx.core:core-ktx"], + "allowedVersions": "<1.18" + }, + { + "description": "See the androidx.core rule above — same compileSdk 36 coupling, androidx.lifecycle side (#2234).", + "matchManagers": ["gradle"], + "matchPackageNames": ["androidx.lifecycle:lifecycle-runtime-compose"], + "allowedVersions": "<2.11" } ] }