Skip to content

Conversation

@einsteinx2
Copy link
Contributor

Summary

Braze informed us that versions 11.0 and 11.1 have a critical bug and requested that we raise our minimum dependency version to 11.2.

Note that we were already pinned up to next major, so version 11.2 and above would be pulled in automatically when updating, so this is just an extra precaution.

Testing Plan

  • Was this tested locally? If not, explain why.

Smoke tested in both a CocoaPods and SPM project and ran pod lib lint locally to confirm the podspec.

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

Braze informed us that versions 11.0 and 11.1 have a critical bug and requested that we raise our minimum dependency version to 11.2.

Note that we were already pinned up to next major, so version 11.2 and above would be pulled in automatically when updating, so this is just an extra precaution.
Copy link

@samdozor samdozor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should probably put something in the kit's release notes linking to the braze notice: https://www.braze.com/docs/developer_guide/platform_integration_guides/swift/changelog/#1110

@einsteinx2 einsteinx2 merged commit 03c3ab2 into development Nov 19, 2024
3 checks passed
@einsteinx2 einsteinx2 deleted the fix/6931-bump-min-braze-version-11.2 branch November 19, 2024 18:00
mparticle-automation added a commit that referenced this pull request Nov 19, 2024
# [8.11.0](v8.10.2...v8.11.0) (2024-11-19)

### Bug Fixes

* Bump min Braze SDK to 11.2 ([#102](#102)) ([03c3ab2](03c3ab2))

### Features

* Add sendProductName Option to Braze ([#100](#100)) ([f8deb1e](f8deb1e))
@mparticle-automation
Copy link
Collaborator

🎉 This PR is included in version 8.11.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants