Release: 2.29.1 - #235
Conversation
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Warning Review limit reached
Next review available in: 24 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe release updates package and Android SDK versions to 2.29.1, adds changelog entries for versions 2.29.1 and 2.29.0, and documents the repository release workflow. ChangesRelease metadata
Estimated code review effort: 1 (Trivial) | ~5 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 |
|
PR Summary: Release: bump to 2.29.1 — add release notes, version bumps, and repository release guidance.
|
PR Summary by QodoRelease 2.29.1: bump RN wrapper + native SDK pins
AI Description
Diagram
High-Level Assessment
Files changed (6)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTo customize comments, go to the Qodo configuration screen, or learn more in the docs. |
|
Reviewed up to commit:415dff84a6327bb2a58825f0dacc4c0141c4f766 Additional Suggestionandroid/build.gradle.kts, line:2reactNativeVersion is set to "+" which allows Gradle to resolve any matching version and can produce non-deterministic builds across environments. Consider pinning this to the specific React Native version(s) this SDK is tested against or document/lock the allowed range to avoid accidental upgrades during CI/consumer resolution.Others- This release commit updated package.json (version + iosPackageVersion) but did not include the regenerated lockfiles or updated sample Podfile lock. Per the repo release checklist you must: 1) run npm install to regenerate package-lock.json and commit package-lock.json; 2) cd sample/ios && bundle exec pod repo update && bundle exec pod update UsercentricsUI to update sample/ios/Podfile.lock and commit that file. Missing these makes CI/native dependency resolution fail and can break downstream consumers.# After bumping versions in package.json and android/build.gradle.kts
# 1) Regenerate root lockfile
npm install
# This updates package-lock.json with version 2.29.1 and any dependency metadata.
# 2) Update iOS sample Podfile.lock
cd sample/ios
bundle exec pod repo update
bundle exec pod update UsercentricsUI
# 3) Commit all version-related files
# - CHANGELOG.md
# - package.json
# - package-lock.json
# - android/build.gradle.kts
# - sample/ios/Podfile.lock |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 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 `@CLAUDE.md`:
- Around line 32-40: Update both fenced code blocks in the changelog and commit
templates in CLAUDE.md to include language identifiers: use markdown for the
changelog template and text for the commit template, preserving their existing
contents.
- Line 82: Remove the CLAUDE.md change from the Release: 2.29.1 commit by
amending or moving it out of that commit. Ensure the release commit contains
only CHANGELOG.md, package.json, package-lock.json, android/build.gradle.kts,
and sample/ios/Podfile.lock.
In `@package.json`:
- Around line 3-10: Resolve the native artifact version mismatch before
finalizing the release: publish Android Maven and iOS CocoaPods artifacts for
2.29.1, or align package.json version and iosPackageVersion plus the native
version in android/build.gradle.kts to an existing supported release. Keep all
package and native SDK versions consistent.
🪄 Autofix
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: 8ec64571-d21c-411b-bb5b-fd9627fc1250
⛔ 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 (4)
CHANGELOG.mdCLAUDE.mdandroid/build.gradle.ktspackage.json
… 2.29.1 UsercentricsCore.denyAll and denyAllForTCF gained a new unsavedServiceDecisions parameter in the native iOS SDK 2.29.1 (statistical exception support). The Kotlin common interface defaults it to null, but that default isn't carried over to the generated Swift/ObjC interop, so the RN wrapper failed to compile against the bumped native SDK version. Pass nil from RNUsercentricsModule.swift for both call sites, preserving the existing public JS API and behavior (nil means no unsaved service decisions are considered, matching pre-2.29.1 semantics per UsercentricsSDKImpl.denyAll). Updated the FakeUsercentricsManager test mock to match the new protocol signature. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Usercentrics 2.29.1 added a required isExempt parameter to several native init signatures used by test mocks (UsercentricsService, ServiceConsentTemplate, SubConsentTemplate, UsercentricsCategory). Update CMPData+Mock.swift to pass isExempt: false, matching pre-2.29.1 (non-exempt) semantics. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
CodeAnt-AI Description
Release React Native SDK 2.29.1 with the latest consent features and fixes
What Changed
Impact
✅ Access to the latest consent and mediation features✅ Fewer banner, link, and content-loading failures✅ More reliable consent navigation across Android, iOS, and TV💡 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
New Features
Documentation
Chores