-
Notifications
You must be signed in to change notification settings - Fork 5
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 aws-sdk is breaking the build 🚨 #35
Comments
After pinning to 2.350.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.352.0See changelog for more information. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.353.0See changelog for more information. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.354.0See changelog for more information. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.355.0See changelog for more information. CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.356.0See changelog for more information. CommitsThe new version differs by 7 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.357.0See changelog for more information. CommitsThe new version differs by 27 commits.
There are 27 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.358.0See changelog for more information. 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 🚀 Release Notes for Release v2.359.0See changelog for more information. CommitsThe new version differs by 30 commits.
There are 30 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.360.0See changelog for more information. CommitsThe new version differs by 31 commits.
There are 31 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.361.0See changelog for more information. CommitsThe new version differs by 32 commits.
There are 32 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.362.0See changelog for more information. 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 🚀 Release Notes for Release v2.363.0See changelog for more information. CommitsThe new version differs by 39 commits.
There are 39 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.364.0See changelog for more information. CommitsThe new version differs by 40 commits.
There are 40 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.365.0See changelog for more information. CommitsThe new version differs by 43 commits.
There are 43 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.366.0See changelog for more information. CommitsThe new version differs by 44 commits.
There are 44 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.367.0See changelog for more information. CommitsThe new version differs by 45 commits.
There are 45 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.368.0See changelog for more information. CommitsThe new version differs by 47 commits.
There are 47 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for Release v2.369.0See changelog for more information. 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 🚀 Release Notes for Release v2.370.0See changelog for more information. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.371.0See changelog for more information. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.372.0See changelog for more information. CommitsThe new version differs by 7 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.373.0See changelog for more information. 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 Release v2.374.0See changelog for more information. CommitsThe new version differs by 11 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.375.0See changelog for more information. CommitsThe new version differs by 12 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.376.0See changelog for more information. CommitsThe new version differs by 13 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.377.0See changelog for more information. CommitsThe new version differs by 17 commits.
There are 17 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.378.0See changelog for more information. CommitsThe new version differs by 18 commits.
There are 18 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.379.0See changelog for more information. CommitsThe new version differs by 31 commits.
There are 31 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.380.0See changelog for more information. CommitsThe new version differs by 32 commits.
There are 32 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.381.0See changelog for more information. CommitsThe new version differs by 41 commits.
There are 41 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.382.0See changelog for more information. 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 🚀 Release Notes for Release v2.383.0See changelog for more information. CommitsThe new version differs by 55 commits.
There are 55 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.387.0See changelog for more information. CommitsThe new version differs by 73 commits.
There are 73 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.388.0See changelog for more information. CommitsThe new version differs by 74 commits.
There are 74 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.389.0See changelog for more information. CommitsThe new version differs by 75 commits.
There are 75 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.390.0See changelog for more information. CommitsThe new version differs by 77 commits.
There are 77 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Release v2.391.0See changelog for more information. CommitsThe new version differs by 78 commits.
There are 78 commits in total. See the full diff |
The dependency aws-sdk was updated from
2.350.0
to2.351.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
aws-sdk 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 Release v2.351.0
See changelog for more information.
Commits
The new version differs by 3 commits.
70cbaa7
Updates SDK to v2.351.0
4073d3d
Merge pull request #2342 from srchase/npmignore-additions
13b0dd3
updated npmignore, fix for issue #2341
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: