chore: [v3.0.0] Merge release into master

[jansegre]

Automated PR to merge branch into based on release event.

Summary by CodeRabbit

• Chores
  • Updated package version to 3.0.0.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.94%. Comparing base (8483779) to head (7b0d1eb).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #1065       +/-   ##
===========================================
+ Coverage   66.33%   87.94%   +21.60%     
===========================================
  Files         114      114               
  Lines        8918     8918               
  Branches     2022     2032       +10     
===========================================
+ Hits         5916     7843     +1927     
+ Misses       2975     1047     -1928     
- Partials       27       28        +1     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 86b20f44-9cc1-4d11-8ada-3d41f3a6ac07

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

The package version in package.json was incremented from 2.17.0 to 3.0.0. No other package metadata, dependencies, scripts, or configuration values were modified. This represents a major version release bump.

Changes

Cohort / File(s)	Summary
Version Bump package.json	Updated version from 2.17.0 to 3.0.0 (major version release).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: [v2.16.0] Merge release into master #1031: Modifies the same package.json version field in a prior release bump.
• chore: [v2.17.0] Merge release into master #1042: Also updates the package.json version field as part of sequential version increments (2.16.0 → 2.17.0 → 3.0.0).

Suggested reviewers

• raul-oliveira
• pedroferreira1

Poem

🐰 A hop and a bound, the version takes flight,
From two-point-seventeen to three, oh what a sight!
Major release hops into the warren today,
A new chapter unfolds in the Hathor-way! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly describes the main change: merging a release (v3.0.0) into the master branch, which matches the package version bump from 2.17.0 to 3.0.0 shown in the changeset.
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 unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/sync-release-v3.0.0

---

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.}