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

github-bot pushed a change to branch dependabot/uv/google-auth-2.48.0
in repository https://gitbox.apache.org/repos/asf/iceberg-python.git


    omit e24034be Build: Bump google-auth from 2.47.0 to 2.48.0
     add b2b4cae4 Build: Bump huggingface-hub from 1.3.2 to 1.3.4 (#2961)
     add f83826d1 Build: Bump mypy-boto3-dynamodb from 1.42.3 to 1.42.33 (#2962)
     add e688ff1e Build: Bump jupyterlab from 4.5.2 to 4.5.3 (#2963)
     add 4baba8fa Build: Bump duckdb from 1.4.3 to 1.4.4 (#2964)
     add 785db90f Build: Bump sqlalchemy from 2.0.45 to 2.0.46 (#2966)
     add 1aa292c7 Build: Bump google-auth from 2.47.0 to 2.48.0

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   (e24034be)
            \
             N -- N -- N   refs/heads/dependabot/uv/google-auth-2.48.0 
(1aa292c7)

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:
 uv.lock | 181 +++++++++++++++++++++++++++++++++-------------------------------
 1 file changed, 94 insertions(+), 87 deletions(-)

Reply via email to