-
Notifications
You must be signed in to change notification settings - Fork 24
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
An in-range update of jsdom is breaking the build 🚨 #530
Comments
After pinning to 11.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 11.4.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 34 commits.
|
Version 11.5.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 |
Version 11.5.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 41 commits.
|
Version 11.6.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 85 commits.
There are 85 commits in total. See the full diff |
Version 11.6.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 11.6.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 11.7.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 15 commits.
See the full diff |
Version 11.8.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 11.9.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 11.10.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 11 commits.
See the full diff |
Version 11.11.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
Version 11.12.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 22 commits.
There are 22 commits in total. See the full diff |
Version 11.3.0 of jsdom just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As jsdom is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Commits
The new version differs by 36 commits.
6bb5885
Version 11.3.0
19183e8
Overhaul how we run web-platform-tests
2d51af3
Update ESLint rules and pass all of them
3bdd8f0
Update dependencies and dev dependencies
44bd291
Add CompositionEvent and WheelEvent
af5a215
Clean up some UI events' init functions
2595ec9
Make FocusEventImpl extend UIEventImpl
44f820b
Check Window type in UIEvent
52e2000
Make Window's impl's wrapper point to global proxy
baf6ea8
Upgrade to webidl2js v8.0.0
b4c6a89
Standardize around impl class names
a55d98e
Convert DOMTokenList to IDL
1d4ecca
Implement attributes.getAttributeValue per spec
fe79937
Update and according to spec
683e942
Speed up sync XHR
There are 36 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: