Release: 2.28.2 - #231
Conversation
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
🤖 CodeAnt AI — Review Status
Updated in place by CodeAnt AI · last 5 reviews |
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
📝 WalkthroughWalkthroughVersion 2.28.2 release metadata was applied to the npm, iOS, and Android package configuration, and a changelog entry documents the included iOS and TCF consent behavior fixes. Changes2.28.2 Release Update
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
codeant-ai
Bot
added
the
size:S
PR Summary by QodoRelease 2.28.2: bump SDK versions + update changelog
AI Description
Diagram
High-Level Assessment
Files changed (5)
|
|
PR Summary: Release 2.28.2: bump package versions and changelog; fixes for iOS build issues and TCF/Consent-or-Pay consent state handling.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Around line 2-3: Update the Fixes heading under release 2.28.2 from level-two
to level-four Markdown heading, preserving the release heading as level three
and maintaining consistent changelog hierarchy.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: b2fa42d6-d304-4d00-8623-e65e1473a6bb
⛔ Files ignored due to path filters (2)
package-lock.jsonis excluded by!**/package-lock.jsonsample/ios/Podfile.lockis excluded by!**/*.lock
📒 Files selected for processing (3)
CHANGELOG.mdandroid/build.gradle.ktspackage.json
| ### 2.28.2 – Jul 22, 2026 | ||
| ## Fixes |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Keep the changelog heading hierarchy consistent.
The release is a ### heading, so Fixes should be a child heading such as #### Fixes, not ## Fixes. This prevents the subsection from appearing above its release in document navigation.
Suggested fix
### 2.28.2 – Jul 22, 2026
-## Fixes
+#### Fixes📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### 2.28.2 – Jul 22, 2026 | |
| ## Fixes | |
| ### 2.28.2 – Jul 22, 2026 | |
| #### Fixes |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CHANGELOG.md` around lines 2 - 3, Update the Fixes heading under release
2.28.2 from level-two to level-four Markdown heading, preserving the release
heading as level three and maintaining consistent changelog hierarchy.
Code Review by Qodo
1. Changelog heading hierarchy
|
![qodo-code-review[bot]](https://avatars.githubusercontent.com/in/484649?s=60&v=4){kind=small}
| ### 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) |
There was a problem hiding this comment.
1. Changelog heading hierarchy 🐞 Bug ⚙ Maintainability
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
### Issue description
`CHANGELOG.md` uses a level-3 release heading (`### 2.28.2 …`) followed immediately by a level-2 section heading (`## Fixes`), which breaks heading nesting and makes sections harder to navigate/parse.
### Issue Context
The same pattern is present in older entries (e.g., 2.28.1), so this PR is not introducing a new pattern but is adding another instance of it.
### Fix Focus Areas
- CHANGELOG.md[2-11]
### Suggested fix
Choose a consistent hierarchy and apply it (ideally across the whole changelog):
- Option A: Make releases `## 2.28.2 …` and subsections `### Fixes`, `### Chores`, etc.
- Option B: Keep releases as `### …` and change subsections to `#### Fixes`, `#### Chores`, etc.
Apply the chosen option at least to the newly added 2.28.2 entry (and preferably to the rest of the file for consistency).
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
![pantoaibot[bot]](https://avatars.githubusercontent.com/in/934356?s=60&v=4){kind=small}
| "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", |
There was a problem hiding this comment.
[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.
| @@ -1,4 +1,4 @@ | |||
| val usercentricsVersion = "2.28.1" | |||
| val usercentricsVersion = "2.28.2" | |||
There was a problem hiding this comment.
[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).
| ### 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 |
There was a problem hiding this comment.
[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.
|
Reviewed up to commit:cb74f4b2d3924ff4444dbc8112833c4af49d5e53 |
1 participant
User description
Summary
package.json,package-lock.json, andandroid/build.gradle.ktssample/ios/Podfile.lockto pinUsercentricsUI/Usercentrics2.28.2Test plan
yarn compile(TS build) passesyarn test— 34/34 passingyarn lint— pre-existing warnings/errors only, unrelated to this diff (verified via stash comparison)pod installinsample/iosresolvesUsercentricsUI (2.28.2)cleanly./gradlew :app:dependenciesresolvescom.usercentrics.sdk:usercentrics-ui:2.28.2— BUILD SUCCESSFUL🤖 Generated with Claude Code
CodeAnt-AI Description
Release 2.28.2 with iOS and consent-state fixes
What Changed
Impact
✅ Successful installs on Xcode 26.6✅ Fewer consent-state mismatches after app start✅ Clearer TCF consent screens💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by CodeRabbit