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
Remove Windows 32-bit Support #17962
Labels
Comments
jennifer-shehane
added
OS: windows
stage: proposal 💡
No work has been done of this issue
type: breaking change
Requires a new major release version
labels
Sep 1, 2021
cypress-bot
bot
added
stage: backlog
and removed
stage: proposal 💡
No work has been done of this issue
labels
Sep 9, 2021
To provide some context on why we feel this change should not impact users too adversely:
|
3 tasks
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
stage: work in progress
and removed
stage: work in progress
stage: needs review
The PR code is done & tested, needs review
labels
Oct 25, 2021
cypress-bot
bot
added
stage: work in progress
stage: needs review
The PR code is done & tested, needs review
and removed
stage: needs review
The PR code is done & tested, needs review
stage: work in progress
labels
Oct 27, 2021
The code for this is done in cypress-io/cypress#18630, but has yet to be released. |
cypress-bot
bot
removed
the
stage: needs review
The PR code is done & tested, needs review
label
Oct 29, 2021
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What would you like?
Drop official support for Win32 operating system.
Why is this needed?
The main goal is to move our internal testing off of Appveyor, it’s slow to run tests, so it slows down every single PR we make. We are only using Appveyor because we cannot test Win32 in CircleCI.
Previous in progress work: #5550
Other
From initial findings, it seems testing Cypress in Win32 is not widely used, but we'd love to hear from anyone about how this may impact their testing.
The text was updated successfully, but these errors were encountered: