Skip to content

chore: Update to Version 9.0.0 - #109

Closed
BrandonStalnaker wants to merge 1 commit into
developmentfrom
chore/SDKE-773/Version-9.0
Closed

chore: Update to Version 9.0.0#109
BrandonStalnaker wants to merge 1 commit into
developmentfrom
chore/SDKE-773/Version-9.0

Conversation

@BrandonStalnaker

Copy link
Copy Markdown
Contributor

Summary

  • Bumps the integration version from 8.11.1 to 9.0.0
  • Updates the mParticle-Apple-SDK dependency to ~> 9.0 for both iOS and tvOS platforms in the podspec
  • Updates the Swift Package Manager dependency to .upToNextMajor(from: "9.0.0") in Package.swift

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

@BrandonStalnaker BrandonStalnaker self-assigned this Jan 28, 2026
@davidzampier

Copy link
Copy Markdown

@BrandonStalnaker does your team have plans to update the Braze version as well? This kit is restraining Braze to v12 (they are on v14), and they've released an important fix for UISceneDelegate recently https://github.com/braze-inc/braze-swift-sdk/releases/tag/14.0.1.

@nickolas-dimitrakas

Copy link
Copy Markdown

Closing this out as obsolete. Since core 9.x we have moved the Apple kits into the mParticle Apple SDK monorepo and aligned the kit release version with the core SDK version line.

The current core README documents adding kits from version-tracked mirror repositories and shows the Braze 14 kit on the 9.x line, for example pod "mParticle-Braze-14", "~> 9" / the mparticle-apple-integration-braze-14 SPM repo. The core Kits/README.md also documents the new kit model: choose the kit track that matches the partner SDK major (braze-12, braze-13, braze-14) and install from the standalone mirror repo.

Because this PR targets the legacy Appboy kit repo and only bumps it to core 9.0.0, it has been superseded by the monorepo-based Braze kit tracks. For Braze 14.x support specifically, use mparticle-apple-integration-braze-14 / mParticle-Braze-14 on the 9.x SDK line.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants