This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/go_modules/github.com/pterm/pterm-0.12.80
in repository https://gitbox.apache.org/repos/asf/iceberg-go.git
discard 7ee865d build(deps): bump github.com/pterm/pterm from 0.12.79 to
0.12.80
add 23c02b2 Update `tabulario/iceberg-rest` to
`apache/iceberg-rest-fixture` (#222)
add c37146b build(deps): bump github.com/aws/aws-sdk-go-v2/service/s3
(#225)
add 71cd1ad build(deps): bump golang.org/x/sync from 0.9.0 to 0.10.0
(#223)
add 63ba03e build(deps): bump github.com/stretchr/testify from 1.9.0 to
1.10.0 (#218)
add a701ade use the right file name (#203)
add 2a572a7 build(deps): bump github.com/pterm/pterm from 0.12.79 to
0.12.80
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 (7ee865d)
\
N -- N -- N
refs/heads/dependabot/go_modules/github.com/pterm/pterm-0.12.80 (2a572a7)
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:
dev/docker-compose.yml | 2 +-
dev/release/release_rc.sh | 2 +-
go.mod | 20 ++++++++++----------
go.sum | 40 ++++++++++++++++++++--------------------
4 files changed, 32 insertions(+), 32 deletions(-)
