fix(ci): pin isolated-kit gradle version to prevent 6.0.0-rc.1 pull#714
Conversation
The isolated urbanairship-kit lint/test steps in daily.yml and the kit-compatibility test in pull-request.yml run `./gradlew` from inside the kit dir without `-Pversion=...`. The kit's standalone build.gradle defaults `project.version = '+'`, so its `com.mparticle:android-kit-plugin` dependency resolves to the highest version on Maven Central — now `6.0.0-rc.1` (published 2026-05-22), which renamed/removed kit-base symbols and broke the kit's compile. Mirror the pattern already used in the Sonatype Release job: extract the SDK version via `./gradlew -q properties` and pass it as `-Pversion=...` to every standalone kit invocation, so it resolves the freshly-published mavenLocal artifact instead of the RC. Affected steps: - lint-checks → Run Isolated Kit Lint (urbanairship-kit) - kotlin-lint-checks → Run Isolated Kit Kotlin Lint (urbanairship-kit) - update-kits → Test Isolated Kits (urbanairship-kit) - kit-compatibility-test → Run Isolated Kit Compatibility Tests (urbanairship-kit) The companion defensive fix in mparticle-android-integration-urbanairship pins the kit's standalone `project.version` to `[5.0,6.0)`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PR SummaryLow Risk Overview That stops isolated kit builds from using the kit default Reviewed by Cursor Bugbot for commit 1b9d339. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
## [5.79.1](v5.79.0...v5.79.1) (2026-05-27) ### Bug Fixes * **ci:** pin isolated-kit gradle version to prevent 6.0.0-rc.1 pull ([#714](#714)) ([eff10ea](eff10ea)) ### Updates & Maintenance * bump trunk-io/trunk-action from 1.2.4 to 1.3.1 ([#705](#705)) ([f4ceca7](f4ceca7)) * Update submodules ([e435979](e435979))
|
🎉 This PR is included in version 5.79.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |



Summary
urbanairship-kitbuild invocations indaily.ymlandpull-request.ymlto the SDK version we're currently building, so they no longer resolve+tocom.mparticle:android-kit-plugin:6.0.0-rc.1on Maven Central.release.yml's Sonatype Release job.Why
The 2026-05-27 release run failed with two distinct errors, both in the urbanairship-kit isolated steps:
Root cause: the kit's standalone
build.gradledefaultsproject.version = '+'. With6.0.0-rc.1published to Maven Central on 2026-05-22,+resolves to the RC, which renamedKitIntegration.AttributeListener→ModifyIdentityListenerand replaced the kit-plugin's task layout. The fix is to pass-Pversion=<sdk-version>so the kit resolves the freshly-publishedmavenLocalartifact instead.Every PR's
Kit Compatibility Testhas been silently red since 2026-05-22 for the same reason.Companion changes
Defense-in-depth pin on the kit's standalone
project.version:External-consumer fixes for #710:
Test plan
Release SDKworkflow (dry run).Lint Checks,Kotlin Lint Checks, andUpdate Kitsshould all pass through the urbanairship-kit isolated step.Kit Compatibility Testis green.🤖 Generated with Claude Code