pnpm@11 defaults prevent updating Cypress directly after release

[MikeMcC399]

Situation

pnpm@11.0.0 introduced a breaking change of setting the configuration parameter minimumReleaseAge to 1440 minutes (1 day).

Attempting to install cypress@latest immediately after a release, falls back to installing a previous version that satisfies the requirements minimumReleaseAge. This is a disadvantage when running the npm script update:cypress to update Cypress to the latest version for each package manager (npm, pnpm, Yarn v1 & Yarn Modern), as it leaves the pnpm examples lagging behind.

Note: this does not affect updates carried out by Renovate.

Suggestion

Configure the pnpm examples with minimumReleaseAgeExclude for cypress:

• examples/basic-pnpm
• examples/start-and-pnpm-workspaces

Increase minimumReleaseAge to 4320 minutes (3 days)

[MikeMcC399]

I am currently unable to action this suggestion because pull request creation has been disabled.

[mschile]

Hi @MikeMcC399 👋🏼, thanks for your patience. You should be able to create a pull request now (I'm still working through the other repos).

[MikeMcC399]

@mschile

You should be able to create a pull request now (I'm still working through the other repos).

• Thank you! I was now able to submit test: exclude cypress from pnpm minimum age checks #1764 to resolve this issue.

[github-actions]

🎉 This issue has been resolved in version 7.4.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀