-
Notifications
You must be signed in to change notification settings - Fork 69
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 resolve is breaking the build 🚨 #255
Comments
After pinning to 1.14.0 your tests are passing again. Downgrade this dependency 📌. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 12 commits ahead by 12, behind by 1.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 15 commits ahead by 15, behind by 1.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 17 commits ahead by 17, behind by 1.
There are 17 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 20 commits ahead by 20, behind by 1.
There are 20 commits in total. See the full diff |
The dependency resolve was updated from
1.14.0
to1.14.1
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
resolve 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 2 commits.
7eb98ea
1.14.1
fe73a76
[Fix]
core
:wasi
was mistakenly available as a core module in v13.4.0See 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: