chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 4am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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
Lockfile-only updates in example projects; no application or action source changes, though refreshed transitive deps could affect CI if installs behave differently.

Overview
Refreshes lock files only under examples/ (npm, pnpm, and yarn) via scheduled lock-file maintenance—no package.json manifest changes.

Across Cypress-focused examples, transitive dev dependencies move to newer patch/minor releases, including qs (6.15.x → 6.16.0), systeminformation (5.31–5.33.x → 5.33.10+), and terminal helpers like ansi-regex and string-width. systeminformation also picks up a stricter Node engine floor (>=10.0.0).

The component-tests example additionally bumps its Vite toolchain (vite 8.2 → 8.3, rolldown 1.2.5 → 1.2.8, related @rolldown/* bindings, postcss, picomatch, nanoid) and react / react-dom (19.2.x → 19.3.0 with scheduler 0.28.0).

The nextjs example lockfile updates next and @next/* (16.3.3 → 16.3.4), sharp / @img/sharp-* (0.35.3 → 0.35.4), matching React 19.3, and related build deps.

A few locks only reshuffle metadata (e.g. dropping redundant root version fields, arch hoisting under clipboardy vs cypress in config/start examples).

^{Reviewed by Cursor Bugbot for commit 1da1b99. 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.

[MikeMcC399]

• see also chore(deps): set npm min-release-age to 7 days #1882 to possibly mitigate the mismatch errors between npm and Renovate waits

[MikeMcC399]

Merging this PR should mitigate multiple reported vulnerabilities in transient dependencies of examples.

[jennifer-shehane]

Merge conflicts now need addressing

[MikeMcC399]

Merge conflicts now need addressing

Renovate did that automatically

[MikeMcC399]

I'm still getting vulnerability alerts from Dependabot.

[cursor]

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

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

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

[MikeMcC399]

Renovate is experiencing some compatibility issues following a version rollout.

I suggest to hold back this PR.

Closing it is not effective because it's an evergreen and it will just get recreated with the same issues.

[MikeMcC399]

This should be good to go, however I'm going to close it and let Renovate recreate so that we have a clear review from Cursor on it.