fix: align braze-38 SDK range with its directory major#730
Conversation
PR SummaryLow Risk Overview This is a Gradle dependency range-only change; no kit source or integration logic is modified in the diff. Reviewed by Cursor Bugbot for commit ed07111. Bugbot is set up for automated code reviews on this repo. Configure here. |
The kit directory suffix N encodes the wrapped vendor SDK's intended major version, but braze/braze-38 pinned com.braze:android-sdk-ui:[37.0.0,38.0.0) (major 37). Bumped to [38.0.0,39.0.0) to match the braze-38 directory; siblings braze-39/40/41 already align and there is no braze-37 directory. The GA kit (ga-23/ga4-23) major-23 alignment is deferred to a separate PR that also bumps the repo Kotlin toolchain, because firebase-analytics 23.x ships Kotlin 2.1/2.2 metadata that the current Kotlin 2.0.20 compiler cannot read. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
608bb3f to
ed07111
Compare
|
319bae2
into
workstation/6.0-Release



Summary
The kit directory suffix
N(e.g.kits/braze/braze-38) encodes the intended major version of the wrapped vendor SDK.braze/braze-38pinned a range that resolved to the wrong major:braze/braze-38com.braze:android-sdk-ui:[37.0.0,38.0.0)(→ 37.x)[38.0.0,39.0.0)Siblings
braze-39/40/41already align, and there is nobraze-37directory, so the range was the defect.Verification
build-kits / Build braze-38passes with the new range.com.braze:android-sdk-ui:38.0.0is published, so the range resolves.Scope change
This PR originally also bumped the GA kits (
ga-23/ga4-23) to firebase-analytics major 23. That is removed here and moved to a dedicated PR, because firebase-analytics 23.x ships Kotlin 2.1/2.2 metadata that the repo's current Kotlin 2.0.20 compiler cannot read — so GA-23 must be coupled with a repo-wide Kotlin toolchain upgrade.The pre-existing
cross-platform-testsfailure (fails on:android:buildSrc:compileKotlin+ emulator infra, unrelated to this change) is not addressed here.🤖 Generated with Claude Code