Skip to content

Release: 2.27.3 - #221

Closed
asadraza-usercentrics wants to merge 1 commit into
masterfrom
release/2.27.3
Closed

Release: 2.27.3#221
asadraza-usercentrics wants to merge 1 commit into
masterfrom
release/2.27.3

Conversation

@asadraza-usercentrics

@asadraza-usercentrics asadraza-usercentrics commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Chores
    • Updated the app/package version to 2.27.3.
    • Brought the Android and iOS package versions in sync with the latest release.
    • Updated a mobile SDK dependency to the newer 2.27.3 release.

@codeant-ai

codeant-ai Bot commented Jun 25, 2026

Copy link
Copy Markdown

Skipping CodeAnt AI review — this PR is a back-merge between long-lived branches (release/2.27.3master). 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 Jun 25, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Updates the published package version and iOS package version in package.json, and bumps the Android usercentricsVersion constant to 2.27.3.

Changes

Release version bump

Layer / File(s) Summary
Version metadata update
package.json, android/build.gradle.kts
package.json version fields and the Android usercentricsVersion constant are updated from 2.27.1 to 2.27.3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

Review effort 1/5, size:M

Suggested reviewers

  • uc-brunosouza
  • uc-brunosilva
  • islameldesoky95

Poem

🐰 I hop from 2.27.1 to 2.27.3,
With tiny taps on a version spree.
Android shuffles, iOS nods bright,
Package numbers gleam in the night.
Hoppy release, all neat and tight.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches the version-bump release change and accurately summarizes the main update.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/2.27.3

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.

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Release 2.27.3: bump JS, iOS, and Android version constants
⚙️ Configuration changes 🕐 Less than 5 minutes

Grey Divider

Description

• Bump React Native package version to 2.27.3 for release publishing.
• Align iOS package version metadata to 2.27.3.
• Update Android Gradle version constant to 2.27.3.
High-Level Assessment

The approach (synchronized version bumps across package.json and Android Gradle config) is the standard, lowest-risk way to cut a release. No meaningful alternative would improve maintainability or reduce risk here.

Files changed (2) +3 / -3

Other (2) +3 / -3
build.gradle.ktsBump Android SDK version constant to 2.27.3 +1/-1

Bump Android SDK version constant to 2.27.3

• Updates the 'usercentricsVersion' constant from 2.27.1 to 2.27.3 to match the release version.

android/build.gradle.kts

package.jsonBump npm package + iOS package metadata to 2.27.3 +2/-2

Bump npm package + iOS package metadata to 2.27.3

• Updates the JavaScript package 'version' and 'iosPackageVersion' fields from 2.27.1 to 2.27.3 for release alignment and publishing.

package.json

@pantoaibot

pantoaibot Bot commented Jun 25, 2026

Copy link
Copy Markdown

PR Summary:

Release: 2.27.3 — version bump for Android and npm/iOS package

  • android/build.gradle.kts: updated usercentricsVersion from 2.27.1 → 2.27.3.
  • package.json: bumped package "version" and "iosPackageVersion" from 2.27.1 → 2.27.3.
  • No functional, structural, or behavioral code changes; no other dependencies or build config modified.

Reviewed by Panto AI

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 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 `@android/build.gradle.kts`:
- Line 1: The Android build variants are out of sync because build.gradle.kts
updates usercentricsVersion while build-legacy.gradle still uses
usercentrics_version at an older value; update the legacy constant too so both
Gradle paths reference the same Usercentrics SDK version and stay aligned.
🪄 Autofix (Beta)

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

Run ID: 9877e5bb-ba12-4004-a62a-e9dca5d3265f

📥 Commits

Reviewing files that changed from the base of the PR and between 1514998 and dea17dd.

⛔ Files ignored due to path filters (3)
  • package-lock.json is excluded by !**/package-lock.json
  • sample/ios/Podfile.lock is excluded by !**/*.lock
  • sample/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • android/build.gradle.kts
  • package.json

Comment thread android/build.gradle.kts
@@ -1,4 +1,4 @@
val usercentricsVersion = "2.27.1"
val usercentricsVersion = "2.27.3"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Align Android SDK version constants across Gradle variants

Line 1 bumps usercentricsVersion to 2.27.3, but android/build-legacy.gradle still pins usercentrics_version to 2.27.1. That creates version drift between build paths and can publish/test different SDK versions unintentionally.

Suggested fix
-// android/build-legacy.gradle
-def usercentrics_version = "2.27.1"
+// android/build-legacy.gradle
+def usercentrics_version = "2.27.3"
🤖 Prompt for 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.

In `@android/build.gradle.kts` at line 1, The Android build variants are out of
sync because build.gradle.kts updates usercentricsVersion while
build-legacy.gradle still uses usercentrics_version at an older value; update
the legacy constant too so both Gradle paths reference the same Usercentrics SDK
version and stay aligned.

Comment thread package.json
Comment on lines +3 to +10
"version": "2.27.3",
"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.27.1",
"iosPackageVersion": "2.27.3",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[VALIDATION] You updated "version" and "iosPackageVersion" to 2.27.3 in package.json. Before publishing, verify that the corresponding native artifacts for 2.27.3 exist and are published: - Android: com.usercentrics.sdk:usercentrics-ui:2.27.3 on your Maven repo(s) (used by android/build.gradle.kts implementation("com.usercentrics.sdk:usercentrics-ui:$usercentricsVersion")). - iOS: CocoaPods/Carthage release UsercentricsUI 2.27.3 (react-native-usercentrics.podspec consumes package['iosPackageVersion'], see podspec reference lines 6-36). If the native artifacts are not yet published, coordinate the native SDK release or revert the bump until they are available to avoid broken installs for consumers.

@pantoaibot

pantoaibot Bot commented Jun 25, 2026

Copy link
Copy Markdown

Reviewed up to commit:dea17dd223a4cc9f5f5bc9a591d86127b8ca7f2e

Additional Suggestion
android/build-legacy.gradle, line:1 The Kotlin DSL build file (android/build.gradle.kts) was bumped to 2.27.3 (see changed line 1). The legacy Groovy build file (android/build-legacy.gradle) still defines def usercentrics_version = "2.27.1" (reference: android/build-legacy.gradle lines 1-16). This creates an inconsistent version state that can cause published artifacts, CI tasks, or legacy build flows to use the wrong SDK version. Update def usercentrics_version to "2.27.3" and ensure version usercentrics_version is consistent across all Android build files and publishing steps. Also run a quick build/publish dry-run to confirm nothing else relies on the old value.
def usercentrics_version = "2.27.3"
version usercentrics_version

buildscript {
    ext.kotlin_version = '1.8.0'

    ext.safeExtGet = { prop, fallback ->
        return rootProject.ext.has(prop) ? rootProject.ext.get(prop) : fallback
    }

    repositories {
        google()
        mavenCentral()
    }

    dependencies {
Others - CHANGELOG.md currently lists 2.27.1 as the latest documented release. Update the changelog to include the 2.27.3 entry (or point to the correct release notes) so consumers and release automation reflect the new package version. This prevents confusion for downstream integrators and release automation that relies on the changelog.
[Release Notes](https://docs.usercentrics.com/cmp_in_app_sdk/latest/about/history/)

### 2.27.3 – Jun 25, 2026
## Fixes
* Align React Native bridge with native Usercentrics SDK 2.27.3 (Android: `usercentrics-ui` 
  version `${usercentricsVersion}`, iOS: `UsercentricsUI` version `${package['iosPackageVersion']}`)
* Updated Android Gradle configuration to consume Usercentrics SDK `2.27.3`
* Updated npm package metadata (`version` and `iosPackageVersion`) to `2.27.3` for consistency

### 2.27.1 – Jun 15, 2026
## Fixes
* **[iOS — Accessibility]** Fixed VoiceOver announcing wrong language for English content (WCAG 3.1.2 Language of Parts)
* **[iOS — Accessibility]** Fixed table in second layer not semantically exposed to VoiceOver (WCAG 1.3.1 Info and Relationships)
* **[iOS — Accessibility]** Fixed CMP links not announced as links by VoiceOver (WCAG 4.1.2 Name, Role, Value)
* **[iOS — Accessibility]** Fixed VoiceOver focus not restored to language picker after language switch (WCAG 3.2.1 On Focus)
* **[iOS — Accessibility]** Added visible focus indicator for all assistive technologies (WCAG 2.4.7 Focus Visible)
* **[iOS]** Fixed crash when tapping service info icon (ⓘ) in Second Layer Categories tab
* **[iOS]** Fixed UI work not dispatched to main thread in `showFirstLayer`; added guard against double-presentation
* **[Android/iOS]** Restored button order to `[denyAll, acceptAll]` in default button mapping
* **[PUR]** Fixed vendor consents not set to `true` when `showTogglesForVendors=false` on second layer Save
  • After bumping versions, run a repo-wide search (eg. grep -R "2.27.1" || git grep) and update any remaining occurrences (CI workflows, Dockerfiles, docs, scripts, example apps, tags) to avoid stale references. Also ensure package-lock / yarn.lock / any generated files are updated (or regenerated) where necessary so published packages and examples remain consistent.

Reviewed by Panto AI

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

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

Grey Divider


Remediation recommended

1. Legacy Gradle version skew 🐞 Bug ≡ Correctness
Description
The PR updates the Android dependency version to 2.27.3 in android/build.gradle.kts, but
android/build-legacy.gradle still pins Usercentrics UI to 2.27.1. Any downstream flow that uses the
legacy Gradle script (it is shipped in the npm package) will resolve an older SDK than intended for
the 2.27.3 release.
Code

android/build.gradle.kts[1]

+val usercentricsVersion = "2.27.3"
Evidence
The release bumps the main Android dependency version to 2.27.3, but the shipped legacy Gradle
script still resolves usercentrics-ui 2.27.1, so consumers using that file will not get the intended
SDK version.

android/build.gradle.kts[1-2]
android/build-legacy.gradle[1-2]
android/build-legacy.gradle[70-75]
package.json[12-16]

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 Android version bump to `2.27.3` was applied only to `android/build.gradle.kts`. The legacy build script `android/build-legacy.gradle` still hardcodes `2.27.1`, creating a shipped version skew for consumers who still rely on that legacy path.

## Issue Context
The `android/` folder is included in the published npm package, so `build-legacy.gradle` is distributed even if it is not the default build entrypoint.

## Fix Focus Areas
- android/build-legacy.gradle[1-2]
- android/build-legacy.gradle[70-75]
- package.json[12-16]

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



Informational

2. Changelog version mismatch 🐞 Bug ⚙ Maintainability
Description
package.json is bumped to 2.27.3, but CHANGELOG.md still shows 2.27.1 as the latest version header.
This makes the in-repo release notes inconsistent with the published version.
Code

package.json[3]

+  "version": "2.27.3",
Evidence
The package version is 2.27.3 while the changelog’s latest visible entry at the top of the file is
2.27.1, indicating the changelog was not updated alongside the release bump.

package.json[1-4]
CHANGELOG.md[1-6]

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 repo version is now `2.27.3`, but the top of `CHANGELOG.md` still lists `2.27.1` as the latest entry, which can confuse users looking for release notes matching the published package.

## Issue Context
If 2.27.3 is a no-change republish, consider adding a brief 2.27.3 entry that explicitly states that.

## Fix Focus Areas
- CHANGELOG.md[1-6]
- package.json[1-4]

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


Grey Divider

Qodo Logo

@uc-brunosilva
uc-brunosilva deleted the release/2.27.3 branch June 25, 2026 08:31
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.

2 participants