Skip to content

Release: 2.28.2 - #232

Merged
uc-brunosilva merged 2 commits into
masterfrom
release/2.28.2
Jul 23, 2026
Merged

Release: 2.28.2#232
uc-brunosilva merged 2 commits into
masterfrom
release/2.28.2

Conversation

@uc-brunosilva

Copy link
Copy Markdown
Collaborator

No description provided.

uc-brunosilva and others added 2 commits July 23, 2026 10:41
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@codeant-ai

codeant-ai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Skipping CodeAnt AI review — this PR is a back-merge between long-lived branches (release/2.28.2master). The diff here has already been reviewed when the underlying commits landed on the source branch, so re-running analysis would produce duplicate findings on already-reviewed code.

If you want to analyze this anyway (e.g. you resolved conflicts with new logic), comment @codeant-ai : review and CodeAnt will start a review.

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@uc-brunosilva, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 45 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 5c2362a2-9eb5-4359-804d-2261a2cc4ea6

📥 Commits

Reviewing files that changed from the base of the PR and between b197309 and cb74f4b.

⛔ Files ignored due to path filters (2)
  • package-lock.json is excluded by !**/package-lock.json
  • sample/ios/Podfile.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • CHANGELOG.md
  • android/build.gradle.kts
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/2.28.2

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@pantoaibot

pantoaibot Bot commented Jul 23, 2026

Copy link
Copy Markdown

PR Summary:

Release 2.28.2: bumped package and gradle versions and added release notes describing iOS build fix and several TCF/PUR bug fixes.

  • Files changed: CHANGELOG.md (added 2.28.2 notes), android/build.gradle.kts (usercentricsVersion -> 2.28.2), package.json (version and iosPackageVersion -> 2.28.2).
  • Key fixes (from changelog):
    • iOS: Rebuilt UsercentricsUI.xcframework with Xcode 26 / Swift 6.3.3 to fix build failures on Xcode 26.6 (includes React Native bridge consumers).
    • PUR: Fixed Consent-or-Pay mandatory purposes silently overriding persisted TCF consent state on SDK initialization (resolves desync between SDK getters and TC string).
    • TCF: Removed Special Purposes from first-layer banner; fixed purposes/special-features being disclosed in second layer and included in TC string when no vendor declared them (issue with Stacks).
  • No source/API code changes in this PR beyond version bumps and the changelog; update dependency to 2.28.2 to pick up the fixes.

Reviewed by Panto AI

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Release 2.28.2: version bumps + changelog entry

📝 Documentation ⚙️ Configuration changes 🕐 10-20 Minutes

Grey Divider

AI Description

• Add 2.28.2 release notes covering iOS toolchain rebuild and TCF/PUR fixes
• Bump SDK/package versions to 2.28.2 across Android, NPM, and iOS sample lockfile
• Align iOS sample dependencies to Usercentrics/UsercentricsUI 2.28.2
Diagram

graph TD
  R(["Release 2.28.2"]) --> C["CHANGELOG.md"] --> N{{"NPM registry"}}
  R(["Release 2.28.2"]) --> P["package.json / lock"] --> N{{"NPM registry"}}
  R(["Release 2.28.2"]) --> G["android/build.gradle.kts"] --> M{{"Maven/Gradle consumers"}}
  R(["Release 2.28.2"]) --> L["sample/ios/Podfile.lock"] --> A{{"CocoaPods consumers"}}
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Automate versioning + changelog (Changesets/standard-version)
  • ➕ Reduces risk of forgetting one of the version touchpoints (NPM + Gradle + iOS package fields)
  • ➕ Produces consistent release commits/tags and repeatable changelog formatting
  • ➕ Easier to validate release contents in CI
  • ➖ Adds tooling and process overhead
  • ➖ May require custom scripting for multi-ecosystem alignment (Gradle + CocoaPods + NPM)
2. Single source of truth for version (generate files during release)
  • ➕ Eliminates manual drift between package.json, Gradle constants, and sample lockfiles
  • ➕ Makes it easier to audit/verify the released version
  • ➖ Requires build/release pipeline changes
  • ➖ Local development may become less transparent if files are generated

Recommendation: For this PR, the manual aligned bumps are acceptable given the small scope and typical release-branch workflow. Longer-term, consider adopting a release automation tool (or a single-source version file) to prevent cross-ecosystem version drift and to make releases more repeatable.

Files changed (5) +20 / -13

Documentation (1) +7 / -0
CHANGELOG.mdAdd 2.28.2 release notes +7/-0

Add 2.28.2 release notes

• Adds a new 2.28.2 entry describing iOS toolchain rebuild and multiple consent/TCF-related fixes. Keeps prior 2.28.1 notes intact.

CHANGELOG.md

Other (4) +13 / -13
build.gradle.ktsBump Android usercentricsVersion to 2.28.2 +1/-1

Bump Android usercentricsVersion to 2.28.2

• Updates the Android build configuration constant from 2.28.1 to 2.28.2 to align artifact consumption with the release.

android/build.gradle.kts

package-lock.jsonUpdate NPM lockfile version to 2.28.2 +2/-2

Update NPM lockfile version to 2.28.2

• Updates the root package version fields in the lockfile from 2.28.1 to 2.28.2 to match the release.

package-lock.json

package.jsonBump NPM package + iOS package version to 2.28.2 +2/-2

Bump NPM package + iOS package version to 2.28.2

• Updates the published NPM package version and the iosPackageVersion field from 2.28.1 to 2.28.2 to reflect the new release.

package.json

Podfile.lockAlign iOS sample pods to Usercentrics 2.28.2 +8/-8

Align iOS sample pods to Usercentrics 2.28.2

• Updates the sample app’s resolved pods to react-native-usercentrics 2.28.2, including Usercentrics and UsercentricsUI, with corresponding checksum updates.

sample/ios/Podfile.lock

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Qodo Logo

Comment thread android/build.gradle.kts
Comment thread package.json
@pantoaibot

pantoaibot Bot commented Jul 23, 2026

Copy link
Copy Markdown

Reviewed up to commit:cb74f4b2d3924ff4444dbc8112833c4af49d5e53

Reviewed by Panto AI

@uc-brunosilva
uc-brunosilva merged commit 3380b40 into master Jul 23, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants