chore: bump native SDK dependency to 2.31.1 - #246
uc-brunosilva wants to merge 1 commit into
Conversation
Validated: npm install, sample Android gradle dependency resolution (usercentrics-ui:2.31.1), and sample iOS pod install/update all resolve cleanly against the real published 2.31.1 artifacts. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
🤖 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 · |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe package metadata and Android Usercentrics dependency version were updated from 2.31.0 to 2.31.1. ChangesVersion alignment
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to The supported Android, iOS, and package version metadata are aligned to 2.31.1, with no confirmed merge-blocking risk. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 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:XS
PR Summary by QodoBump native Usercentrics SDKs to 2.31.1
AI Description
Diagram
High-Level Assessment
Files changed (4)
|
Code Review by Qodo
1. Readers miss the 2.31.1 release notes
|
![qodo-code-review[bot]](https://avatars.githubusercontent.com/in/484649?s=60&v=4){kind=small}
| { | ||
| "name": "@usercentrics/react-native-sdk", | ||
| "version": "2.31.0", | ||
| "version": "2.31.1", |
There was a problem hiding this comment.
1. Readers miss the 2.31.1 release notes 📘 Rule violation ⚙ Maintainability
package.json advances the distributable package version to 2.31.1, but CHANGELOG.md still begins with 2.31.0 and has no entry documenting the native dependency bump. When the release workflow publishes this version, consumers and maintainers have no repository record of the fixes and compliance changes included in the release.
Agent Prompt
## Issue description
The package version is being advanced to `2.31.1`, but the changelog has no corresponding newest-first entry documenting the fixes and compliance changes in the release.
## Fix Focus Areas
- CHANGELOG.md[1-2]
## Recommended Fix
Add `### 2.31.1 – Sep 16, 2026` above the `2.31.0` entry, following the existing heading and component-entry formats. Use only approved native `2.31.1` fixes and compliance release notes, such as a `## Chores` entry recording the native Usercentrics SDK bump to `2.31.1`; do not invent wording if approved release-note content is unavailable.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
|
PR Summary: Bumps the native Usercentrics SDK version to 2.31.1 across project metadata.
|
![pantoaibot[bot]](https://avatars.githubusercontent.com/in/934356?s=60&v=4){kind=small}
| { | ||
| "name": "@usercentrics/react-native-sdk", | ||
| "version": "2.31.0", | ||
| "version": "2.31.1", |
There was a problem hiding this comment.
[VALIDATION] Regenerate and commit the lockfile after this package.json version bump (run npm install or yarn install depending on repo policy) so package-lock.json (or yarn.lock) contains the new version. Also run the prepare/compile step (npm/yarn install triggers prepare) locally to ensure tsc succeeds and produced lib/ artifacts are valid before pushing the bump.
|
Reviewed up to commit:1b96fa64a4c89eb13648292a9422453297d322ce Additional SuggestionOthers- Before merging, verify the bumped native artifacts (Android Maven artifact com.usercentrics.sdk:usercentrics-ui:2.31.1 and iOS pods Usercentrics(2.31.1)/UsercentricsUI(2.31.1)) are published and resolvable from your CI/dev machines. The CLAUDE.md pre-flight checklist requires confirming the native SDK is published (see CLAUDE.md pre-flight steps). Merging this bump when the native artifacts are not yet available will break Gradle sync / pod install in CI and for consumers. - Run the CocoaPods update step described in the release checklist to update the sample app's Podfile.lock: cd sample/ios && bundle exec pod repo update && bundle exec pod update UsercentricsUI. Commit the updated Podfile.lock so the sample app points to 2.31.1 (react-native podspec pulls iosPackageVersion from package.json; see react-native-usercentrics.podspec which depends on UsercentricsUI "#{package['iosPackageVersion']}" at lines 6-36). Failing to update Podfile.lock can cause confusion and CI failures when validating the sample app.cd sample/ios
bundle exec pod repo update
bundle exec pod update UsercentricsUIAfter running these commands, commit the updated
### 2.31.1 – Sep 16, 2026
## Fixes
* **[Core]** Bumped native Usercentrics SDK to 2.31.1 (compliance and bugfix release; no React Native API changes) |
1 participant
User description
Bumps the native Usercentrics SDK dependency from 2.31.0 to 2.31.1.
No RN-side API changes needed — 2.31.1 is fixes/compliance only, no public API changes.
Validated locally:
npm install(+prepare/tsccompile) — clean./gradlew :app:dependenciesresolvescom.usercentrics.sdk:usercentrics-ui:2.31.1→usercentrics:2.31.1→usercentrics-android:2.31.1pod update UsercentricsUIresolvesUsercentrics (2.31.1)/UsercentricsUI (2.31.1)against the real published CocoaPods trunk artifacts🤖 Generated with Claude Code
CodeAnt-AI Description
Align the React Native package and native dependencies with SDK version 2.31.1
What Changed
Impact
✅ Access to native SDK 2.31.1 fixes and compliance updates✅ Consistent Android, iOS, and React Native package versions💡 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