-
Notifications
You must be signed in to change notification settings - Fork 25
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 seneca is breaking the build 🚨 #129
Comments
After pinning to 3.7.0 your tests are passing again. Downgrade this dependency 📌. |
Your tests are still failing with this version. Compare changes |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 11 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 20 commits.
There are 20 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 26 commits.
There are 26 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 28 commits.
There are 28 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 38 commits.
There are 38 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 48 commits.
There are 48 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 54 commits.
There are 54 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 56 commits.
There are 56 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 57 commits.
There are 57 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 59 commits.
There are 59 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 78 commits.
There are 78 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 80 commits.
There are 80 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 83 commits.
There are 83 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 13 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 26 commits.
There are 26 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 28 commits.
There are 28 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 29 commits.
There are 29 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 32 commits.
There are 32 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 20 commits.
There are 20 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 33 commits.
There are 33 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes |
The devDependency seneca was updated from
3.7.0
to3.8.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
seneca 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
Commits
The new version differs by 44 commits.
0ce5048
v3.8.0
27cbd79
allow ~ in plugin names
00dee63
fix promise ready
3db9083
doc
e083e0c
mark remote msgs
124237e
detect other error types
a994def
v3.8.0-rc3
0b23a94
test-plugin
50ac810
check func
8f5c888
plugin ignore log
a10de5e
support @seneca/ org module prefix as plugin name prefix
29970b0
use-plugin@3.0; plugin tag separator now uniformly $ not /
b9f8941
api impl cleanup
b5fa9fb
seneca-transport 2.4.0
d12ae5c
local plugin error codes support by fail method
There are 44 commits in total.
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: