chore(deps): set pnpm minimumReleaseAge to 10080 minutes (7 days)

[MikeMcC399]

• supports resolution of issue Renovate and various package manager min age unaligned #1816

Situation

The renovate.json configuration includes:

    "minimumReleaseAge": "7 days",
    {
      "matchPackageNames": ["cypress"],
      "minimumReleaseAge": "0 days"
    }

pnpm examples are set up with minimumReleaseAge of 4320 in minutes. This is equivalent to 3 days.

An exception for cypress is in place using minimumreleaseageexclude.

Change

In pnpm examples:

• examples/basic-pnpm/pnpm-workspace.yaml
• examples/start-and-pnpm-workspaces/pnpm-workspace.yaml

update minimumReleaseAge:

BEFORE	AFTER
4320 minutes (3 days)	10080 minutes (7 days)

Execute pnpm update --recursive --save to update all dependencies according to changed age rules.

Verification

Using Ubuntu 24.04.4 LTS with Node.js 24.18.0 LTS execute:

npm install pnpm@latest -g
git clean -xfd
cd examples
cd basic-pnpm
pnpm update --recursive --save
cd ..
cd start-and-pnpm-workspaces
pnpm update --recursive --save
cd ..
cd ..

Confirm logs show:

✓ Lockfile passes supply-chain policies (167 entries in 1.2s)

---

Note

Low Risk
Example-only pnpm policy and lockfile updates with no application or CI workflow logic changes.

Overview
Raises pnpm minimumReleaseAge from 4320 (3 days) to 10080 (7 days) in examples/basic-pnpm and examples/start-and-pnpm-workspaces, matching Renovate’s 7 days policy while keeping cypress on minimumReleaseAgeExclude.

Lockfiles were refreshed under the stricter age rules, bumping transitive deps qs (6.15.2 → 6.15.3) and systeminformation (5.31.7 → 5.31.11) in both example projects.

^{Reviewed by Cursor Bugbot for commit fdaa5c0. Bugbot is set up for automated code reviews on this repo. 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.