chore(release): pull main into develop post release v3.4.0

[MoumitaM]

PR Description

Please include a summary of the change along with the relevant motivation and context.

Linear task (optional)

Linear task link

Cross Browser Tests

Please confirm you have tested for the following browsers:

• Chrome
• Firefox
• IE11

Sanity Suite

• All sanity suite test cases pass locally

Security

• The code changed/added as part of this pull request won't create any security issues with how the software is being used.

Summary by CodeRabbit

• Bug Fixes
  • Fixed a dependency issue in the analytics package to enhance stability.
• Updates
  • Updated a key dependency in the sanity suite for improved performance.
• Chores
  • Updated project version to reflect the latest changes and improvements.

[coderabbitai]

Walkthrough

The updates encompass a crucial bug fix in the analytics-v1.1 package, an upgrade in the sanity-suite package dependencies, and a version increment in the project's configuration. Specifically, the analytics-v1.1 package resolved a dependency issue, while the sanity-suite received a newer version of rudder-sdk-js. Additionally, the project version was bumped up in the sonar-project.properties file, indicating progress and refinement in the project's development cycle.

Changes

File(s)	Change Summary
packages/analytics-v1.1/CHANGELOG.md	Moved analytics common to dev dependencies in rudder-sdk-js
packages/sanity-suite/CHANGELOG.md	Updated rudder-sdk-js to 3.0.3
sonar-project.properties	Updated project version from 3.3.0 to 3.4.0

🐰✨
To code, to fix, a hop and a skip,
In the land of bugs, we made a flip.
From 2.48.6, oh what a mix,
To 3.0.3, with a magic trick.
🌟📦
Across the meadows, under the moon,
Our project grows, it'll be ready soon!

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.90%. Comparing base (395f9b9) to head (08ab4c1).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #1676   +/-   ##
========================================
  Coverage    53.90%   53.90%           
========================================
  Files          461      461           
  Lines        15611    15611           
  Branches      3102     3091   -11     
========================================
  Hits          8415     8415           
- Misses        5890     5907   +17     
+ Partials      1306     1289   -17     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between d31252e and 08ab4c1.

Files ignored due to path filters (5)

• package-lock.json is excluded by: !**/*.json
• package.json is excluded by: !**/*.json
• packages/analytics-v1.1/package.json is excluded by: !**/*.json
• packages/analytics-v1.1/project.json is excluded by: !**/*.json
• packages/sanity-suite/package.json is excluded by: !**/*.json

Files selected for processing (4)

• packages/analytics-v1.1/CHANGELOG.md (1 hunks)
• packages/analytics-v1.1/CHANGELOG_LATEST.md (1 hunks)
• packages/sanity-suite/CHANGELOG.md (1 hunks)
• sonar-project.properties (1 hunks)

Files skipped from review due to trivial changes (2)

• packages/sanity-suite/CHANGELOG.md
• sonar-project.properties

Additional comments: 2

packages/analytics-v1.1/CHANGELOG_LATEST.md (1)

• 1-6: The changelog entry for version 2.48.6 is clear and follows the conventional format, including a detailed description of the bug fix and relevant links. This change, moving the analytics common package to dev dependencies, is a good practice for dependency management, potentially reducing unnecessary production dependencies.

packages/analytics-v1.1/CHANGELOG.md (1)

• 5-11: The CHANGELOG update for version 2.48.6 is well-documented, following conventional formatting practices. It clearly outlines the bug fix and includes relevant links for traceability. This is a good practice for maintaining project history and facilitating understanding of changes.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[github-actions]

size-limit report 📦

Name	Size (Base)	Size (Current)	Size Limit	Status
Common Code - No bundling	15.81 KB	15.81 KB (0%)	16.5 KB	✅
Remote Module Federation Mapping - CDN	330 B	330 B (0%)	512 B	✅
Remote Module Federated Plugins - CDN	5.71 KB	5.71 KB (0%)	6 KB	✅
Core ESM - NPM	7.64 KB	7.64 KB (0%)	8 KB	✅
Core CJS - NPM	22.45 KB	22.45 KB (0%)	23 KB	✅
Core - NPM	22.55 KB	22.55 KB (0%)	23 KB	✅
Core Legacy - CDN	42.99 KB	42.99 KB (0%)	44 KB	✅
Core - CDN	22.71 KB	22.71 KB (0%)	23 KB	✅
Core (legacy build) - CDN - v1.1	31.52 KB	31.55 KB (+0.1% ▲)	32 KB	✅
Core - NPM - v1.1	31.54 KB	31.53 KB (-0.03% ▼)	32 KB	✅
Service Worker Module	22.64 KB	22.64 KB (0%)	24 KB	✅
All Integrations (legacy build) - CDN	98.57 KB	98.57 KB (0%)	105 KB	✅