Closed
Conversation
|
CodeAnt AI is reviewing your PR. Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
Review Summary by QodoRelease version 2.26.1 with GPP framework support
WalkthroughsDescription• Bumped version from 2.25.1 to 2.26.1 across build files • Updated CHANGELOG with new features and fixes for release • Updated package.json and Android build configuration versions Diagramflowchart LR
A["Version 2.25.1"] -- "bump version" --> B["Version 2.26.1"]
B -- "update" --> C["build.gradle.kts"]
B -- "update" --> D["package.json"]
B -- "document" --> E["CHANGELOG.md"]
File Changes1. android/build.gradle.kts
|
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 reviewⓘ The new review experience is currently in Beta. Learn more |
codeant-ai
bot
added
the
size:S
|
CodeAnt AI finished reviewing your PR. |
|
PR Summary: Release 2.26.1: Adds US National (GPP) support, extends GPP API to mobile/game engine bridges, exposes DPS metadata via new getDpsMetadata() API, makes TCF resurfacing period configurable, and includes several bug fixes; also bumps package and Android build version constants.
|
uc-brunosilva
requested review from
asadraza-usercentrics,
islameldesoky95,
rodrigo-leal-usercentrics and
uc-christiansousa
![pantoaibot[bot]](https://avatars.githubusercontent.com/in/934356?s=60&v=4){kind=small}
Comment on lines
+2
to
+11
| ### 2.26.1 – Apr 07, 2026 | ||
| ## Features | ||
| * Added support for US National (GPP) privacy framework | ||
| * Extended GPP API to Flutter, React Native and Unity bridges | ||
| * Exposed DPS metadata via new `getDpsMetadata()` API | ||
| * TCF resurfacing period now configurable via Admin UI (1–13 months) | ||
| ## Fixes | ||
| * Fixed TCF resurfacing period logic | ||
| * Fixed stored information not shown on DPS details | ||
| * Fixed TCF maintain legitimate interest logic on Deny All |
There was a problem hiding this comment.
[NITPICK] The new release entry uses the date 'Apr 07, 2026' which is in the future relative to today (2026-04-06). Update the release date to the actual publish date or ensure this intentional future date won't break release automation, CI validations, or downstream documentation that expects chronological ordering.
Comment on lines
+3
to
+10
| "version": "2.26.1", | ||
| "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.25.1", | ||
| "iosPackageVersion": "2.26.1", |
There was a problem hiding this comment.
[VALIDATION] You bumped package version and iosPackageVersion to 2.26.1. Ensure you also: 1) run the 'yarn compile' (prepare) to regenerate the lib/ artifacts and include them in the release; 2) run the prepublish codegen script (generate-codegen-jni.js) so native bindings/JNI are updated; 3) verify the podspec (react-native-usercentrics.podspec) picks up the new iosPackageVersion and that CocoaPods integration works with 2.26.1. Also verify CI/publishing scripts and any release tags are updated to avoid publishing mismatches.
|
Reviewed up to commit:fcef129fdc125f9867b836a0b59aa593a02dc6bd Additional Suggestionandroid/build.gradle.kts, line:23-31There is an inconsistency between Android compile SDK versions: build.gradle.kts sets compileSdk = 34 (line ~23) while build-legacy.gradle uses compileSdkVersion 33 (line ~31 in that file). Confirm whether both build entry points must target the same compileSdk; if so, align them or document why they differ. Mismatched compileSdk can lead to subtle compilation/runtime issues for native dependencies.Others- Check other package.json files in the repo (e.g., sample/, example/ or workspace packages) and native release automation (CI, publishing scripts) to ensure the version bump is applied consistently across all distribution artifacts and example apps. Missing updates in supporting packages can cause integration tests or sample apps to reference older SDK versions. |
CI Feedback 🧐A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User description
Release 2.26.1
Features
getDpsMetadata()APIFixes
CodeAnt-AI Description
Release 2.26.1 adds new privacy features and fixes consent behavior issues
What Changed
Impact
✅ Broader privacy compliance support✅ Easier privacy setup across mobile and game apps✅ Fewer consent and DPS display issues💡 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.