-
Notifications
You must be signed in to change notification settings - Fork 24
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 @feathersjs/adapter-commons is breaking the build 🚨 #104
Labels
Comments
After pinning to 4.4.1 your tests are passing again. Downgrade this dependency 📌. |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 9 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes Release Notes for v4.5.24.5.2 (2020-03-04)Bug Fixes
CommitsThe new version differs by 14 commits.
See the full diff |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The dependency @feathersjs/adapter-commons was updated from
4.4.1
to4.4.3
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@feathersjs/adapter-commons 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
Release Notes for v4.4.3
4.4.3 (2019-12-06)
Bug Fixes
Commits
The new version differs by 5 commits.
76d2ab5
chore(release): publish v4.4.3
725d7aa
chore: Skip version that got published with errors
872b669
fix(adapter-commons): Filter arrays in queries (#1724)
7fdd2d6
chore: Update dependencies to enable Greenkeeper 🌴 (#1711)
a75aa09
chore: Update version and 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: