Grouping AWS SDK updates #90
Merged
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
|
#sre |
vmercierfr
force-pushed
the
dependabot-for-aws
branch
from
bac1d8d to
f6ced7d
Compare
Minimum allowed line rate is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Objective
Grouping AWS SDK updates
Why
Dependabot created 26 PRs for AWS SDK updates we activated it a week ago.
AWS releases many patch versions for each AWS module. Because we are using several AWS modules (RDS, Cloudwatch, STS, ...), we are exposed to many PRs to review, which increases the maintenance cost.
Concurrent PRs on the AWS SDK packages also lead to Git conflicts on
go.sum, which are waste to fix.With this change, AWS SDK should be grouped once a week, like hashicorp/aws-sdk-go-base#842.
How
Release plan