[v13] Update dependencies for assets/aws and assets/backport (#26914)#26948
Closed
jentfoo wants to merge 1 commit intobranch/v13from
Closed
[v13] Update dependencies for assets/aws and assets/backport (#26914)#26948jentfoo wants to merge 1 commit intobranch/v13from
assets/aws and assets/backport (#26914)#26948jentfoo wants to merge 1 commit intobranch/v13from
Conversation
* Bump golang.org/x/oauth2 in /assets/backport Bumps [golang.org/x/oauth2](https://github.com/golang/oauth2) from 0.0.0-20211104180415-d3ed0bb246c8 to 0.8.0. - [Commits](https://github.com/golang/oauth2/commits/v0.8.0) --- updated-dependencies: - dependency-name: golang.org/x/oauth2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> * Bump github.com/stretchr/testify from 1.7.0 to 1.8.3 in /assets/backport Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.7.0 to 1.8.3. - [Release notes](https://github.com/stretchr/testify/releases) - [Commits](stretchr/testify@v1.7.0...v1.8.3) --- updated-dependencies: - dependency-name: github.com/stretchr/testify dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> * Bump github.com/gravitational/trace in /assets/backport Bumps [github.com/gravitational/trace](https://github.com/gravitational/trace) from 1.1.15 to 1.2.1. - [Release notes](https://github.com/gravitational/trace/releases) - [Commits](gravitational/trace@v1.1.15...v1.2.1) --- updated-dependencies: - dependency-name: github.com/gravitational/trace dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> * Bump github.com/aws/aws-sdk-go-v2/config in /assets/aws Bumps [github.com/aws/aws-sdk-go-v2/config](https://github.com/aws/aws-sdk-go-v2) from 1.18.12 to 1.18.25. - [Release notes](https://github.com/aws/aws-sdk-go-v2/releases) - [Changelog](https://github.com/aws/aws-sdk-go-v2/blob/main/CHANGELOG.md) - [Commits](aws/aws-sdk-go-v2@config/v1.18.12...config/v1.18.25) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go-v2/config dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> * Bump github.com/aws/aws-sdk-go-v2/service/ec2 in /assets/aws Bumps [github.com/aws/aws-sdk-go-v2/service/ec2](https://github.com/aws/aws-sdk-go-v2) from 1.77.0 to 1.98.0. - [Release notes](https://github.com/aws/aws-sdk-go-v2/releases) - [Changelog](https://github.com/aws/aws-sdk-go-v2/blob/main/CHANGELOG.md) - [Commits](aws/aws-sdk-go-v2@service/ec2/v1.77.0...service/ec2/v1.98.0) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go-v2/service/ec2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
jentfoo
requested review from
adaadb6,
codingllama,
rosstimothy,
wadells and
zmb3
Contributor
|
We don't typically backport dependency updates, is this worth doing? Also, is there a chance these are moving past the base go.mod now? |
Contributor
Author
|
Closing based off @codingllama's feedback. There are no CVE's contained here that need backporting, so I agree this is low value. I thought it may make sense to keep v13 close to master, but I was on the fence myself. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
V13 backport of PR #26914
v11 and v12 do not have
assets/awsand the updates forassets/backportare fairly low priority. For those reasons I was not planning to backport these to v11 or v12. Let me know if anyone feels otherwise.