This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/gradle/org.assertj-assertj-core-3.27.3
in repository https://gitbox.apache.org/repos/asf/iceberg.git
discard fa81c4ae8f Build: Bump org.assertj:assertj-core from 3.27.2 to 3.27.3
add 1a69ff8bcb Build: Bump mkdocs-material from 9.5.49 to 9.5.50 (#12005)
add 4e00a31854 Build: Bump datamodel-code-generator from 0.26.4 to 0.26.5
(#12004)
add 7e0cd3fa1e Revert "API: add hashcode cache in StructType (#11764)"
(#12007)
add ee8bb00518 Build: Bump org.assertj:assertj-core from 3.27.2 to 3.27.3
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 (fa81c4ae8f)
\
N -- N -- N
refs/heads/dependabot/gradle/org.assertj-assertj-core-3.27.3 (ee8bb00518)
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:
api/src/main/java/org/apache/iceberg/types/Types.java | 8 +-------
open-api/requirements.txt | 2 +-
site/requirements.txt | 2 +-
3 files changed, 3 insertions(+), 9 deletions(-)
