MOEN-45786: Dependency Update 2026-07-01 - #128
Conversation
|
🚪 Hodor is reviewing this PR... 👀 |
moe-hodor
Bot
added
branch:unknown
|
Branch: Branching Strategy — unrecognized branch prefix Branch
Posted by Hodor's branching-strategy gate. Per the Branching Strategy, branches must use |
![moe-hodor[bot]](https://avatars.githubusercontent.com/in/3251438?s=60&v=4){kind=small}
| ext { | ||
| moengageNativeBOMVersion = "2.2.1" | ||
| moengagePluginBaseBOMVersion = "3.0.1" | ||
| moengagePluginBaseBOMVersion = "3.1.0" |
There was a problem hiding this comment.
🔴 Critical — Version inconsistency: moengagePluginBaseBOMVersion was updated to 3.1.0 but moengageNativeBOMVersion is still at 2.2.1 while all other modules (cards, core, personalize, geofence) are at 2.3.0.
Impact: When an app uses both Inbox and other modules, Gradle will resolve dependencies from different BOM versions (2.2.1 vs 2.3.0), potentially pulling incompatible artifacts or causing runtime conflicts.
Fix: Update moengageNativeBOMVersion = "2.2.1" to "2.3.0" to match the other modules.
| ext { | ||
| moengageNativeBOMVersion = "2.2.2" | ||
| moengageNativeBOMVersion = "2.3.0" | ||
| moengagePluginBaseBOMVersion = "3.0.1" |
There was a problem hiding this comment.
🔴 Critical — Version inconsistency: moengageNativeBOMVersion was updated to 2.3.0 but moengagePluginBaseBOMVersion is still at 3.0.1 while all other modules (cards, core, inbox, personalize) are at 3.1.0.
Impact: The Geofence module will pull plugin dependencies from BOM 3.0.1 while other modules use 3.1.0, causing version drift and potential incompatibilities in shared plugin-base classes.
Fix: Update moengagePluginBaseBOMVersion = "3.0.1" to "3.1.0" to match the other modules.
There was a problem hiding this comment.
Review: MOEN-45786 Dependency Update 2026-07-01
Branching & CFR: MOEN-45786/dependency_update — category: unknown, impact: ❓ Unknown CFR
MOEN-45786/dependency_update doesn't use a recognized prefix. Per the Branching Strategy, use:
feature/— planned work (neutral CFR)patch/— weekly maintenance (neutral CFR)hotfix/— emergency fix (⚠ increases CFR)revert/— rollback (⚠ increases CFR)
Summary
Automated dependency update for MoEngage React Native SDK:
- Android BOM:
2.2.x→2.3.0 - Plugin BOM:
3.0.1→3.1.0 - iOS plugins: minor version bumps across Cards, Core, Geofence, Inbox, Personalize
Quality Gates
✅ PR Size: 62 lines changed across 15 files — Good size.
✅ Tests: 5 test file(s) modified (CHANGELOGs).
Jira Alignment
MOEN-45786: "React Native Version update for personalize SDK update"
- ✅ PR updates Personalize SDK versions (iOS:
1.0.0→1.1.0, Android BOM bump) ⚠️ No Jira description to validate full scope
Issues Found
- 🔴 Critical: 2 version inconsistency issues
⚠️ Warning: 1 branching strategy violation (from pipeline)
Key Concerns
-
Incomplete Version Updates (🔴 Critical)
sdk/inbox/android/build.gradle:moengageNativeBOMVersionstill at2.2.1while all other modules upgraded to2.3.0sdk/geofence/android/build.gradle:moengagePluginBaseBOMVersionstill at3.0.1while all other modules upgraded to3.1.0- This creates version drift across modules, which can cause runtime conflicts when multiple SDKs are used together
-
Branching Prefix (
⚠️ Warning)- Should use
patch/MOEN-45786-dependency-updatefor maintenance work
- Should use
Regression Risk
Low — This is a dependency version bump with no code changes. However, the version inconsistency issues must be fixed to avoid:
- Module A depending on BOM 2.2.1 and Module B depending on BOM 2.3.0 could cause classpath conflicts
- Plugin dependencies may resolve to incompatible versions
What's Good
✅ CHANGELOG updates are comprehensive and well-documented
✅ iOS .podspec versions are consistently updated across all modules
✅ Android version bumps are applied to most modules correctly
Verdict
REQUEST_CHANGES — Fix the two version inconsistency issues in sdk/inbox and sdk/geofence to ensure all modules use the same BOM versions (2.3.0 for native BOM, 3.1.0 for plugin BOM).
3 participants
Summary
Automated dependency update (target:
both).Platform status