This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/pip/sdks/python/container/py311/urllib3-1.26.17
in repository https://gitbox.apache.org/repos/asf/beam.git
discard 4f5f81ebec2 Bump urllib3 from 1.26.16 to 1.26.17 in
/sdks/python/container/py311
add 1c5982567b3 Bump cloud.google.com/go/bigtable from 1.19.0 to 1.20.0 in
/sdks (#28789)
add 25024064ed2 Bump github.com/aws/aws-sdk-go-v2/config in /sdks (#28790)
add b556aee9177 Bump urllib3 from 1.26.16 to 1.26.17 in
/sdks/python/container/py38 (#28787)
add f4d4de8d815 Bump urllib3 from 1.26.16 to 1.26.17 in
/sdks/python/container/py311
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 (4f5f81ebec2)
\
N -- N -- N
refs/heads/dependabot/pip/sdks/python/container/py311/urllib3-1.26.17
(f4d4de8d815)
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:
sdks/go.mod | 10 +++++-----
sdks/go.sum | 16 ++++++++++------
sdks/python/container/py38/base_image_requirements.txt | 2 +-
3 files changed, 16 insertions(+), 12 deletions(-)
