aws-sdk@2.6.11 breaks build 🚨 #730
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 similar comment
pgte
force-pushed
the
greenkeeper-aws-sdk-2.6.11
branch
from
adf0d17
to
2dfd5cd
Compare
1 similar comment
pgte
force-pushed
the
greenkeeper-aws-sdk-2.6.11
branch
from
2dfd5cd
to
6c92957
Compare
1 similar comment
pgte
force-pushed
the
greenkeeper-aws-sdk-2.6.11
branch
from
6c92957
to
0202aec
Compare
pgte
force-pushed
the
greenkeeper-aws-sdk-2.6.11
branch
from
0202aec
to
f38b810
Compare
pgte
force-pushed
the
greenkeeper-aws-sdk-2.6.11
branch
from
f38b810
to
4c82995
Compare
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if it’s related. Thank you! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
aws-sdk just published its new version 2.6.11.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As aws-sdk is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
See changelog for more information.
The new version differs by 1551 commits .
9611fefUpdates SDK to v2.6.115b4e194Updates region config to support Budgets service05d60f1Adds AWS.Budgets APIa9a6032Updates SDK to v2.6.109832118Merge pull request #1188 from binoculars/patch-1fe2c60fUpdate link to changelog for README8593f8dUpdates SDK to v2.6.923ae71eMerge pull request #1183 from aws/add-dualstack-accelerate557c0c8Merge pull request #1169 from jbergknoff/stream-error-propagationec99a24Adds support for using dualstack with accelerate with S3.471dd1aUpdates SDK to v2.6.832ca3ffadded changelog entry0794efaPropagate an error from a stream to s3.upload callback54a18bbTag release v2.6.7d19c8daUpdates CHANGELOG to v2.6.7There are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade