-
Notifications
You must be signed in to change notification settings - Fork 364
Update Cypress v10 tests to 12.3.0 #725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I suggest to merge this PR independently of any decision to rename the |
checking |
21f307b
to
3b31d14
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @MikeMcC399! I think we should just remove the v10 level in a separate PR to imply cypress(latest) with the additional v9 set.
You're welcome! And thank you for merging!
That makes sense to promote the v12.x examples up a level and remove the v10 label and level. I'll make that the next PR for next week as it will have knock-on effects for any other work, so it will be good to have a new base to work on. |
Love it. Have a great weekend! |
Thanks and same to you! |
🎉 This PR is included in version 5.0.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This PR resolves issue #684 "v10 examples do not use latest version 12.2.0".
Each of the test directories in examples/v10 is upgraded to use Cypress 12.3.0.
The npm-based v10 examples are updated using:
./scripts/npm-install-v10-examples.sh
. This updatespackage.json
to include"cypress": "^12.3.0"
examples/v10/start-and-yarn-workspaces is updated using:
yarn upgrade-interactive --latest
examples/v10/install-command is updated using:
yarn add cypress -D
examples/v10/basic-pnpm is updated using:
pnpm up --latest
A next stage may be to rename the directory examples/v10, or eliminate it, to make it more inline with the Cypress 12.x version being used.