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

github-bot pushed a change to branch 
dependabot/go_modules/github.com/aws/aws-sdk-go-v2/config-1.27.30
in repository https://gitbox.apache.org/repos/asf/iceberg-go.git


 discard 59407fd  build(deps): bump github.com/aws/aws-sdk-go-v2/config
     add c9f9c62  build(deps): bump github.com/aws/aws-sdk-go-v2/service/s3 
(#136)
     add 54f31bd  build(deps): bump github.com/aws/aws-sdk-go-v2/credentials 
(#135)
     add 6e20c65  build(deps): bump github.com/aws/aws-sdk-go-v2/config

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   (59407fd)
            \
             N -- N -- N   
refs/heads/dependabot/go_modules/github.com/aws/aws-sdk-go-v2/config-1.27.30 
(6e20c65)

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:
 go.mod | 2 +-
 go.sum | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

Reply via email to