-
Notifications
You must be signed in to change notification settings - Fork 3
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 juice is breaking the build 🚨 #40
Comments
After pinning to 4.2.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 4.3.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.3.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 35 commits.
There are 35 commits in total. See the full diff |
Version 4.3.0 of juice was just published.
juice
This version is covered by your current version range and after updating it in your project the build failed.
juice is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
Commits
The new version differs by 10 commits.
7c77209
v 4.3.0
4a33ca0
Merge pull request #304 from ldipasquale/master
fb125b6
Add preserveKeyFrames
efe12d4
Merge pull request #302 from bago/fix-build
4b2ae5c
package-lock was outdated and npm install failed
7f12184
Merge pull request #301 from bago/new-test
168cda0
Tests proving #226 is fixed
70986f3
Merge pull request #5 from Automattic/master
8c40486
Merge pull request #300 from bago/patch-1
95b40a5
Added Mosaico email editor reference
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: