This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/pip/python/pydantic-2.0.3
in repository https://gitbox.apache.org/repos/asf/iceberg.git
omit f96d7d0f7b Build: Bump pydantic from 1.10.11 to 2.0.3 in /python
add 9204b2dd17 Spark 3.4: Create non-existing Tag/Branch when using CREATE
OR REPLACE (#8086)
add 4a0daf33b2 Build: Bump aiohttp from 3.8.4 to 3.8.5 in /python (#8119)
add ce40e3c809 Build: Bump fastavro from 1.7.4 to 1.8.2 in /python (#8118)
add 8abf9879a1 Build: Bump pydantic from 1.10.11 to 2.0.3 in /python
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 (f96d7d0f7b)
\
N -- N -- N refs/heads/dependabot/pip/python/pydantic-2.0.3
(8abf9879a1)
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:
python/poetry.lock | 238 ++++++++++-----------
python/pyproject.toml | 2 +-
.../IcebergSqlExtensionsAstBuilder.scala | 4 +
.../plans/logical/CreateOrReplaceBranch.scala | 1 +
.../plans/logical/CreateOrReplaceTag.scala | 1 +
.../datasources/v2/CreateOrReplaceBranchExec.scala | 14 +-
.../datasources/v2/CreateOrReplaceTagExec.scala | 14 +-
.../v2/ExtendedDataSourceV2Strategy.scala | 9 +-
.../iceberg/spark/extensions/TestBranchDDL.java | 67 ++++++
.../iceberg/spark/extensions/TestTagDDL.java | 14 ++
10 files changed, 227 insertions(+), 137 deletions(-)
