-
Notifications
You must be signed in to change notification settings - Fork 16
Release: 2.28.2 #231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release: 2.28.2 #231
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,11 @@ | ||
| [Release Notes](https://docs.usercentrics.com/cmp_in_app_sdk/latest/about/history/) | ||
| ### 2.28.2 – Jul 22, 2026 | ||
| ## Fixes | ||
| * **[iOS]** Rebuilt `UsercentricsUI.xcframework` with the Xcode 26 / Swift 6.3.3 toolchain, fixing build failures on Xcode 26.6 for apps consuming 2.27.1/2.28.0 (including via the React Native bridge) | ||
|
Comment on lines
+2
to
+4
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 1. Changelog heading hierarchy In CHANGELOG.md, the 2.28.2 release header is ### but the following Fixes header is ##, which makes Fixes a higher-level section than the release itself (outline-wise it becomes a peer/parent rather than a subsection). This weakens changelog structure (TOC/navigation/readability) and continues an existing pattern in prior entries. Agent Prompt
|
||
| * **[PUR]** Fixed Consent-or-Pay mandatory purposes silently overriding the user's real TCF consent state on SDK initialization, causing a desync between the SDK's consent getters and the persisted TC string | ||
| * **[TCF]** Removed Special Purposes from the first layer of the TCF banner — not a first-layer requirement | ||
| * **[TCF]** Fixed purposes and special features being disclosed in the second layer (and included in the TC string) even when no vendor declared them, when Stacks are enabled | ||
|
Comment on lines
+2
to
+7
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [VALIDATION] Changelog entry for 2.28.2 describes an iOS xcframework rebuild and fixes that rely on published native artefacts. Please add a short upgrade note to the entry indicating that apps must use UsercentricsUI 2.28.2 (and the date it was published), and confirm the package was pushed to CocoaPods/your binary distribution before release. This will help integrators who hit pod install / build issues after upgrading. ### 2.28.2 – Jul 22, 2026
## Fixes
* **[iOS]** Rebuilt `UsercentricsUI.xcframework` with the Xcode 26 / Swift 6.3.3 toolchain, fixing build failures on Xcode 26.6 for apps consuming 2.27.1/2.28.0 (including via the React Native bridge)
* **[PUR]** Fixed Consent-or-Pay mandatory purposes silently overriding the user's real TCF consent state on SDK initialization, causing a desync between the SDK's consent getters and the persisted TC string
* **[TCF]** Removed Special Purposes from the first layer of the TCF banner — not a first-layer requirement
* **[TCF]** Fixed purposes and special features being disclosed in the second layer (and included in the TC string) even when no vendor declared them, when Stacks are enabled
#### Upgrade notes
* iOS integrators must use `UsercentricsUI` **2.28.2** (published to CocoaPods on **Jul 22, 2026**) when upgrading to `@usercentrics/react-native-sdk` 2.28.2 to avoid Xcode 26.x build issues.
* Ensure `pod repo update` has been run so that CocoaPods can resolve `UsercentricsUI (2.28.2)` correctly. |
||
|
|
||
| ### 2.28.1 – Jul 15, 2026 | ||
| ## Fixes | ||
| * **[iOS — Mediation]** Fixed AppLovin CCPA `setDoNotSell` always passing `YES` regardless of the actual consent value | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| val usercentricsVersion = "2.28.1" | ||
| val usercentricsVersion = "2.28.2" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [REFACTORING] You bumped usercentricsVersion to "2.28.2" (line 1). Consider centralizing this SDK version in a single shared location (or Gradle ext/value file) if multiple modules or sample apps reference it, to avoid drift and duplicate edits in future releases. Also double-check other build files (sample app build.gradle, CI scripts) that may hardcode the older version so nothing is left referencing 2.28.1. The dependency usage occurs in the dependencies block (see android/build.gradle.kts dependency declarations). |
||
| val reactNativeVersion = "+" | ||
|
|
||
| fun BooleanProperty(name: String): Boolean { | ||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,13 +1,13 @@ | ||
| { | ||
| "name": "@usercentrics/react-native-sdk", | ||
| "version": "2.28.1", | ||
| "version": "2.28.2", | ||
| "description": "Usercentrics SDK", | ||
| "homepage": "https://usercentrics.com", | ||
| "main": "lib/index.js", | ||
| "types": "lib/index.d.ts", | ||
| "author": "Usercentrics <developer@usercentrics.com>", | ||
| "iosPackageName": "react-native-usercentrics", | ||
| "iosPackageVersion": "2.28.1", | ||
| "iosPackageVersion": "2.28.2", | ||
|
Comment on lines
+3
to
+10
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [CRITICAL_BUG] You updated both "version" and "iosPackageVersion" in package.json (lines 3 and 10) — ensure the lockfile and all published artefacts are consistent: 1) Commit the corresponding package-lock.json / yarn.lock changes to this PR so consumers and CI install the exact bumped package. 2) Verify the npm publish / release pipeline will include the updated react-native-usercentrics.podspec (it reads package['iosPackageVersion']) and that the external iOS binary (UsercentricsUI 2.28.2) is published to CocoaPods / your internal repo before pushing this release. See react-native-usercentrics.podspec which references package['iosPackageVersion'] and s.version (reference: react-native-usercentrics.podspec lines 6-36). If the CocoaPods artifact is not available, consumers will fail on pod install. |
||
| "license": "SEE LICENSE IN LICENSE", | ||
| "files": [ | ||
| "android", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Keep the changelog heading hierarchy consistent.
The release is a
###heading, soFixesshould be a child heading such as#### Fixes, not## Fixes. This prevents the subsection from appearing above its release in document navigation.Suggested fix
📝 Committable suggestion
🤖 Prompt for AI Agents