fix: pin android-core upper bound to prevent 6.0.0-rc.1 pull#89
Conversation
The open-ended `+` range resolves to the highest available version on Maven Central — now `6.0.0-rc.1` (published 2026-05-22). 6.x removed deprecated symbols, breaking standalone plugin builds. See mParticle/mparticle-android-sdk#710 for the broader incident. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PR SummaryLow Risk Overview CI: the Android unit-test job in Reviewed by Cursor Bugbot for commit 8812639. Bugbot is set up for automated code reviews on this repo. Configure here. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit edd593a. Configure here.
There was a problem hiding this comment.
Pull request overview
This PR aims to prevent Android builds of the Cordova mParticle plugin from resolving com.mparticle:android-core:6.0.0-rc.1 (and newer 6.x pre-releases) by replacing the dynamic + selector with an explicit upper-bounded range in the plugin’s Android Gradle dependency declarations.
Changes:
- Replace
com.mparticle:android-core:+with a bounded version range forcompileOnly. - Apply the same bounded version range for
testImplementation. - Add an inline comment explaining the rationale and linking to the upstream incident.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
android-core 5.79.0 (resolved by the [5.0,6.0) range) is compiled with Java 17 (class file version 61.0). Running the unit-test job on JDK 11 (class file version 55.0) causes a "bad class file" error at compile time. Aligns the android-test job with the example-android job which already uses JDK 17 successfully. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
8812639
Summary
com.mparticle:android-core:+range with[5.0,6.0)inplugin/src/android/build.gradle.testImplementationline.Why
com.mparticle:android-core:6.0.0-rc.1was published to Maven Central on 2026-05-22. The+selector resolves to the highest available version, which is now the RC. 6.x removed deprecated symbols, so anyone consuming this plugin in a fresh build now resolves a kit-base API the plugin source can't compile against.See mParticle/mparticle-android-sdk#710 for the broader incident affecting all Android consumers using dynamic ranges.
Test plan
cordova build androidsucceeds against a project that uses this plugin.🤖 Generated with Claude Code