-
Notifications
You must be signed in to change notification settings - Fork 5
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 jasmine-core is breaking the build 🚨 #16
Comments
After pinning to 2.6.3 your tests are passing again. Downgrade this dependency 📌. |
Version 2.7.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notes2.7.0Please see the release notes. CommitsThe new version differs by 40 commits ahead by 40, behind by 6.
There are 40 commits in total. See the full diff |
Version 2.8.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notes2.8.0Please see the release notes. CommitsThe new version differs by 22 commits.
There are 22 commits in total. See the full diff |
Version 2.9.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notes2.9.0Please see the release notes CommitsThe new version differs by 83 commits.
There are 83 commits in total. See the full diff |
Version 2.9.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notes2.9.1Please see the release notes CommitsThe new version differs by 85 commits.
There are 85 commits in total. See the full diff |
Version 2.99.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 91 commits.
There are 91 commits in total. See the full diff |
Version 2.6.4 of jasmine-core just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As jasmine-core 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
Release Notes
2.6.4Please see the release notes
Commits
The new version differs by 4 commits.
02c18a3
Bump version to 2.6.4
0c6397d
Don't setTimeout() every time the stack is cleared via MessageChannel()
eb46714
Don't use
window
b38decf
Break into a
setTimeout
every once in a whileSee 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: