Repository navigation
chore: ignore Dependabot bumps that need a deliberate migration - #956
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Kotlin migration progressNo change to the Java left to convert.
Conversion progress: 0.0% (16,728 of 16,550 baseline Java LOC left to convert). 132 Java files and 36 Kotlin files in scope. |
Binary compatibility
Compares the release AAR against the same artifact at the last version published to Maven Central; R8-renamed classes and members are excluded (see the script docstring). Full japicmp HTML/XML reports are attached as the |
📦 SDK Size Impact ReportWhat the SDK adds to a minified release APK. mParticle Core SDKMeasured against an empty baseline app. Unlike the Rokt kit, android-core ships no Compose and no resources, so there is nothing here that a host app would already provide.
mParticle Core + Rokt kitMeasured against a Compose + Material3 reference app, so these are the costs on top of an app that already ships Compose. The reference app's dependencies are a documented convention, not a measured average: see
Rokt SDK+ umbrella (adds the payment extension)
➡️ SDK size impact change is minimal. Raw measurementscore, Target branch: {"baseline_dex_bytes": 0, "baseline_download_bytes": 2513, "baseline_install_bytes": 7529, "core_dex_bytes": 220412, "core_download_bytes": 123804, "core_install_bytes": 131057}core, This PR: {"baseline_dex_bytes": 0, "baseline_download_bytes": 2511, "baseline_install_bytes": 7528, "core_dex_bytes": 220412, "core_download_bytes": 123800, "core_install_bytes": 131050}rokt, Target branch: {"baseline_dex_bytes": 1829108, "baseline_download_bytes": 1240062, "baseline_install_bytes": 1300934, "kit_dex_bytes": 4170020, "kit_download_bytes": 2548124, "kit_install_bytes": 2623275, "sdkplus_dex_bytes": 9291568, "sdkplus_download_bytes": 7985700, "sdkplus_install_bytes": 8165359}rokt, This PR: {"baseline_dex_bytes": 1829108, "baseline_download_bytes": 1240062, "baseline_install_bytes": 1300934, "kit_dex_bytes": 4170020, "kit_download_bytes": 2548120, "kit_install_bytes": 2623275, "sdkplus_dex_bytes": 9291568, "sdkplus_download_bytes": 7985699, "sdkplus_install_bytes": 8165359} |
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Why
Dependabot keeps reopening dependency updates that the team has already closed on purpose, because they would break apps that use the SDK or need a planned build migration. The same updates have been closed three times since 12 October and come back each day. Once this lands, Dependabot stops proposing those updates, and patch-level updates to the same dependencies still arrive.
Programme
Standalone change, no programme.
What changes
Before: closing a grouped Dependabot pull request records nothing, so Kotlin 2.4, Gradle 9 and android-media 1.7 updates reopen daily. After:
.github/dependabot.ymlignores minor and major updates for Kotlin (org.jetbrains.kotlin:*,org.jetbrains.kotlin.*and thejvmplugin) andcom.mparticle:android-media, and major updates forgradle-wrapper. Moving to any of these becomes a deliberate change; delete the matching rule when that work starts.Linked work
Related: #940, #941, #942, #945, #946, #947, #948, #949 — the updates closed today that this stops from reopening.
Rollout
Nothing changes in production; if this is wrong, revert the pull request.
Risks
jvmname does not match the build-logic Kotlin plugin; it is the name Dependabot itself uses in those pull requests; we would see abump jvmpull request reappear.Risk class: low.
Who
Written by: an automated coding agent, at a maintainer's request.
Code reviewed before opening: an automated review agent read the change before commit.
Design reviewed before opening: no one.
Decision this implements: the maintainer's triage of open Dependabot pull requests on 19 October 2026.
Checked: the file parses as YAML; dependency names match those in the closed pull requests.
Not checked: Dependabot's behaviour after merge, which shows only on its next scheduled run.
Size
Hand-written: 14 lines in 1 file.
Generated: none.