This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/pip/python/coverage-7.3.0
in repository https://gitbox.apache.org/repos/asf/iceberg.git
omit 3cc2661be5 Build: Bump coverage from 7.2.7 to 7.3.0 in /python
add 9affb38b48 Build: Bump psycopg2-binary from 2.9.6 to 2.9.7 in /python
(#8307)
add 0bcbb2dd25 Build: Bump boto3 from 1.26.161 to 1.28.17 in /python
(#8309)
add 753611da45 Build: Bump mkdocstrings-python from 1.2.1 to 1.3.0 in
/python (#8310)
add 19351f39bc Build: Bump coverage from 7.2.7 to 7.3.0 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 (3cc2661be5)
\
N -- N -- N refs/heads/dependabot/pip/python/coverage-7.3.0
(19351f39bc)
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/mkdocs/requirements.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
