Web SDK Release v2.6.2

[KambleSonam]

Changes

Describe the key changes in this PR with the Jira Issue reference
-Added color scheme for handling background in Adv Builder Web Popup

Changes to Public Facing API if any

Please list the impact on the public facing API if any

How Has This Been Tested?

Describe the testing approach and any relevant configurations (e.g., environment, platform)

Checklist

• Code compiles without errors
• Version Bump added to package.json & CHANGELOG.md
• All tests pass
• Build process is successful
• Documentation has been updated (if needed)
• Automation tests are passing

Link to Deployed SDK

Use these url for testing :

1. https://static.wizrocket.com/staging/<CURRENT_BRANCH_NAME>/js/clevertap.min.js
2. https://static.wizrocket.com/staging/<CURRENT_BRANCH_NAME>/js/sw_webpush.min.js

How to trigger Automations

Just add a empty commit after all your changes are done in the PR with the command

 git commit --allow-empty -m "[run-test] Testing Automation"

This will trigger the automation suite

Summary by CodeRabbit

• New Features

  • Introduced color scheme support for background handling in the Adv Builder Web Popup, improving visual customization options.

• Chores

  • Version bumped to 2.6.2.

[francispereira]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the package version to 2.6.2 and adds a color-scheme: none; CSS property to the web popup iframe styling to disable browser/system color scheme behavior. Documentation is updated accordingly in the changelog.

Changes

Cohort / File(s)	Summary
Release Management CHANGELOG.md, package.json	Version bumped to 2.6.2 with changelog entry documenting the color scheme addition for Adv Builder Web Popup background handling.
Web Popup Styling src/util/campaignRender/webPopup.js	Added color-scheme: none; to IFRAME_STYLE to disable browser/system color scheme behavior on the popup iframe.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

claude-code-assisted

Suggested reviewers

• darshanclevertap

Poem

🐰 A hop, skip, and a version bump to 2.6.2!
With color schemes now disabled, the popup's fresh and bright,
The iframe wears its neutral coat, no system colors in sight,
A tiny tweak, a changelog note—our work is done just right! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description partially follows the template but lacks critical details in the 'Changes' and 'How Has This Been Tested?' sections.	Add the Jira Issue reference to the Changes section and provide specific testing approach details, environment configurations, and platforms used for validation.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Web SDK Release v2.6.2' directly aligns with the main change—a version release bump to 2.6.2 with a single feature addition (color scheme for popup background handling).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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 develop

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

package.json (1)

58-59: ⚠️ Potential issue | 🟡 Minor

Consider alternatives to crypto-js due to discontinuation status.

Both packages verified—no known CVEs for core-js@^3.49.0 or crypto-js@^4.2.0. However, crypto-js has been discontinued and unmaintained since ~2024. While v4.2.0 fixed CVE-2023-46233 and has no current vulnerabilities, the lack of maintenance makes it a maintenance risk. Consider migrating to native Web Crypto API or Node.js crypto module.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 58 - 59, Replace the discontinued dependency
"crypto-js" with a maintained alternative: refactor code that imports or uses
crypto-js to instead use the Node.js "crypto" module (server-side) or the Web
Crypto API (browser-side), update all references where "crypto-js"
functions/classes are used (e.g., encryption/hash helpers) to call the native
APIs, remove "crypto-js" from dependencies in package.json and add any necessary
polyfills only if absolutely required, and keep "core-js" unchanged unless you
need specific polyfills—test and validate that functions doing
hashing/encryption (the modules that currently import "crypto-js") produce
identical outputs.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/util/campaignRender/webPopup.js`:
- Line 35: The CSS rule in src/util/campaignRender/webPopup.js uses an invalid
value "none" for the color-scheme property; update the declaration in the
webPopup CSS block (the color-scheme property) to a valid value (for example
"light", "dark", "light dark", or remove the property entirely) so it conforms
to the spec and browser behavior.

---

Outside diff comments:
In `@package.json`:
- Around line 58-59: Replace the discontinued dependency "crypto-js" with a
maintained alternative: refactor code that imports or uses crypto-js to instead
use the Node.js "crypto" module (server-side) or the Web Crypto API
(browser-side), update all references where "crypto-js" functions/classes are
used (e.g., encryption/hash helpers) to call the native APIs, remove "crypto-js"
from dependencies in package.json and add any necessary polyfills only if
absolutely required, and keep "core-js" unchanged unless you need specific
polyfills—test and validate that functions doing hashing/encryption (the modules
that currently import "crypto-js") produce identical outputs.

🪄 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: 9a0006e0-3990-408e-b2de-341d9547fbcd

📥 Commits

Reviewing files that changed from the base of the PR and between b8d78d3 and 1e011d4.

📒 Files selected for processing (3)

• CHANGELOG.md
• package.json
• src/util/campaignRender/webPopup.js