chore: enable Cypress examples updates with Renovate

[MikeMcC399]

Situation

When a new version of Cypress is released, it is being updated in the examples sub-directories by manually running scripts/update-cypress-latest.sh on Ubuntu and then manually submitting a PR with the changes.

Renovate is already established in this repo, however the settings in renovate.json include extend from config:recommended, which includes :ignoreModulesAndTests with ignorePaths for "**/examples/**".

Change

Modify the renovate.json to update the npm module cypress in the examples sub-directories.

Verification

npx --yes --package renovate -- renovate-config-validator

---

Note

Low Risk
Low risk config-only change that only affects which Renovate PRs are created for cypress under examples/**. Potential impact is limited to increased dependency update PR volume for those example projects.

Overview
Allows Renovate to update the cypress npm dependency inside examples/** by adding a targeted packageRules override, despite the inherited config:recommended ignore settings.

All other Renovate behavior (e.g., disabling dependencies updates generally, grouping eslint updates, scheduling) remains unchanged.

^{Written by Cursor Bugbot for commit 4cfe914. This will update automatically on new commits. Configure here.}

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

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

[cursor]

packageRules cannot override ignorePaths file exclusion

High Severity

The config:recommended preset includes :ignoreModulesAndTests, which sets ignorePaths to include "**/examples/**". This causes Renovate to skip discovering and parsing package files in examples/ directories entirely during the file discovery phase—before packageRules are ever evaluated. The new packageRules entry with "enabled": true and "matchFileNames": ["examples/**"] will never match anything because no packages from those paths exist in Renovate's processing pipeline. The config needs to override ignorePaths (which is non-mergeable) or use "ignorePresets": [":ignoreModulesAndTests"] to actually allow Renovate to discover those package files.