chore(deps): update dependency rimraf to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
rimraf	^2.2.8 → ^6.0.0

---

Release Notes

isaacs/rimraf (rimraf)

v6.1.3

Compare Source

v6.1.2

Compare Source

v6.1.1

Compare Source

v6.1.0

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v5.0.10

Compare Source

v5.0.9

Compare Source

v5.0.8

Compare Source

v5.0.7

Compare Source

v5.0.6

Compare Source

v5.0.5

Compare Source

v5.0.4

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

v4.4.1

Compare Source

v4.4.0

Compare Source

v4.3.1

Compare Source

v4.3.0

Compare Source

v4.2.0

Compare Source

v4.1.4

Compare Source

v4.1.3

Compare Source

v4.1.2

Compare Source

v4.1.1

Compare Source

v4.1.0

Compare Source

v4.0.7

Compare Source

v4.0.6

Compare Source

v4.0.5

Compare Source

v4.0.4

Compare Source

v4.0.3

Compare Source

v4.0.2

Compare Source

v4.0.1

Compare Source

v4.0.0

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

---

Note

Low Risk
Dev-only dependency and lockfile changes with no production code paths affected; main risk is CI/test breakage from rimraf’s major-version API or Node requirements.

Overview
Bumps the devDependency rimraf from ^2.2.8 to ^6.0.0 in package.json and refreshes yarn.lock so the direct install resolves to rimraf 6.x (with a newer glob / minimatch stack than the old glob@7-based rimraf 2.x).

This is dependency-only: no runtime or library source changes. rimraf is still used the same way in tests (e.g. rimraf.sync in tests/test-unix.js); reviewers should confirm test/CI scripts still pass on the repo’s Node version after the major upgrade.

^{Reviewed by Cursor Bugbot for commit 2bea6ed. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cypress-app-bot]

See the guidelines for reviewing dependency updates for info on how to review dependency update PRs.

[cursor]

rimraf v6 breaks rimraf.sync() call in tests

High Severity

Upgrading rimraf from ^2.2.8 to ^6.0.0 breaks the existing usage in tests/test-unix.js. The test file does var rimraf = require('rimraf') followed by rimraf.sync(socket). In rimraf v2, require('rimraf') returned a function with a .sync property. In rimraf v5+, the default export was removed — require('rimraf') now returns an object with named exports like { rimraf, rimrafSync, ... }. The .sync property no longer exists on the module object, so rimraf.sync(socket) will throw a TypeError at runtime.

Additional Locations (1)

• yarn.lock#L5316-L5323

 

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 46ccfc2. Configure here.}

[cursor]

rimraf v6 requires Node 20 breaking declared engine

High Severity

Upgrading rimraf from ^2.2.8 to ^6.0.0 introduces a Node.js engine requirement of 20 || >=22, while the project's engines field declares support for node >= 6. Since rimraf is used in tests/test-unix.js, any CI or developer environment running Node.js versions below 20 (e.g., Node 18) will fail to install or run the dependency, breaking the test suite.

 

^{Reviewed by Cursor Bugbot for commit 46ccfc2. Configure here.}