Release: 2.28.1

[uc-brunosilva]

No description provided.

[codeant-ai]

Skipping CodeAnt AI review — this PR is a back-merge between long-lived branches (release/2.28.1 → master). 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]

Warning

Review limit reached

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

Next review available in: 37 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

Run ID: bdca1373-0f62-403b-b361-2f6d6f1d0f00

📥 Commits

Reviewing files that changed from the base of the PR and between fbca38d and be13b61.

⛔ 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 (2)

• 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.1

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[qodo-code-review]

PR Summary by Qodo

Release 2.28.1: bump SDK versions across JS, Android, and iOS sample

⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Bump React Native SDK package version from 2.28.0 to 2.28.1.
• Align Android Gradle and iOS sample pod lock versions to 2.28.1.
• Update lockfiles to reflect the new release version.

Diagram

graph TD
  A(["Release 2.28.1"]) --> B["package.json"] --> C["package-lock.json"]
  A --> D["android/build.gradle.kts"]
  A --> E["sample/ios/Podfile.lock"]

Loading

High-Level Assessment

The PR follows the standard release approach: update the canonical package versions and synchronize the platform-specific lock/config files. Alternatives (e.g., leaving sample lockfiles untouched) generally increase drift and CI/reproducibility risk.

Files changed (4) +69 / -69

Other (4) +69 / -69

build.gradle.ktsBump Android Usercentrics version to 2.28.1 +1/-1

Bump Android Usercentrics version to 2.28.1

• Updates the Android-side Usercentrics version constant from 2.28.0 to 2.28.1 so builds resolve the released artifact version.

android/build.gradle.kts

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

Update NPM lockfile version to 2.28.1

• Synchronizes the lockfile's top-level package version entries to 2.28.1 to match the release.

package-lock.json

package.jsonBump JS package and iOS package version to 2.28.1 +2/-2

Bump JS package and iOS package version to 2.28.1

• Updates the published NPM package version and the tracked iOS package version from 2.28.0 to 2.28.1.

package.json

Podfile.lockLock iOS sample pods to Usercentrics 2.28.1 +64/-64

Lock iOS sample pods to Usercentrics 2.28.1

• Updates the sample app's locked pod versions for react-native-usercentrics, Usercentrics, and UsercentricsUI to 2.28.1, along with corresponding checksum changes.

sample/ios/Podfile.lock

[pantoaibot]

PR Summary:

Release: patch version bump to 2.28.1.

• android/build.gradle.kts: updated usercentricsVersion from "2.28.0" to "2.28.1".
• package.json: updated "version" and "iosPackageVersion" from "2.28.0" to "2.28.1".
• No functional, logic, dependency, or API changes—only version metadata updates for release.

Reviewed by Panto AI

[pantoaibot]

Reviewed up to commit:be13b616e783ee40997577ea9882a914b418d00e

Reviewed by Panto AI

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Changelog version mismatch 🐞 Bug ⚙ Maintainability

Description

The PR bumps the package version to 2.28.1 but the repository CHANGELOG.md still starts at 2.28.0,
leaving 2.28.1 without a changelog entry. This can cause incorrect or missing release notes for the
2.28.1 release.

Code

package.json[R3-10]

+  "version": "2.28.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.28.0",
+  "iosPackageVersion": "2.28.1",

Evidence

The PR bumps package.json to 2.28.1, but the changelog file’s top entry remains 2.28.0, so 2.28.1
is not documented in the changelog.

package.json[1-12]
CHANGELOG.md[1-10]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The PR updates the published package version to `2.28.1`, but `CHANGELOG.md` does not contain a `2.28.1` section at the top (it currently starts at `2.28.0`). This makes the repo changelog inconsistent with the released version.

### Issue Context
- `package.json` now declares version `2.28.1`.
- `CHANGELOG.md` top entry is still `2.28.0`.

### Fix Focus Areas
- CHANGELOG.md[1-12]

### Suggested change
Add a new heading for `### 2.28.1 – <date>` above the existing `2.28.0` section, and include the relevant notes for this patch release (or explicitly note that it is a metadata-only release if that is intended).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---