This is an automated email from the ASF dual-hosted git repository.

dependabot[bot] pushed a change to branch 
dependabot/go_modules/sdks/github.com/aws/aws-sdk-go-v2/credentials-1.20.3
in repository https://gitbox.apache.org/repos/asf/beam.git


 discard ee0512b4562 Bump github.com/aws/aws-sdk-go-v2/credentials in /sdks
     add f0a19da20a9 Bump github.com/moby/moby/client from 0.5.1 to 0.6.0 in 
/sdks (#40054)
     add f757785ba15 Bump cloud.google.com/go/bigtable from 1.53.0 to 1.56.0 in 
/sdks (#40056)
     add 737972ef463 Bump github.com/aws/aws-sdk-go-v2/service/s3 in /sdks 
(#40053)
     add 830dd3fe076 Bump github.com/aws/aws-sdk-go-v2/credentials in /sdks

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (ee0512b4562)
            \
             N -- N -- N   
refs/heads/dependabot/go_modules/sdks/github.com/aws/aws-sdk-go-v2/credentials-1.20.3
 (830dd3fe076)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 sdks/go.mod | 10 +++++-----
 sdks/go.sum | 20 ++++++++++----------
 2 files changed, 15 insertions(+), 15 deletions(-)

Reply via email to