-
Notifications
You must be signed in to change notification settings - Fork 6
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 rollup is breaking the build 🚨 #43
Comments
After pinning to 1.27.6 your tests are passing again. Downgrade this dependency 📌. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v1.27.82019-12-02 Bug Fixes
Pull Requests |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v1.27.92019-12-07 Bug Fixes
Pull Requests
CommitsThe new version differs by 9 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v1.27.102019-12-11 Bug Fixes
Pull Requests
CommitsThe new version differs by 12 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
The devDependency rollup was updated from
1.27.6
to1.27.7
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
rollup is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Release Notes for v1.27.7
2019-12-01
Bug Fixes
Pull Requests
Commits
The new version differs by 4 commits.
c753a7f
1.27.7
1b8a3de
Update changelog
d5651be
Fix incomplete computed property deoptimization (#3267)
d7e3993
Update changelog
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: