This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/go_modules/sdks/google.golang.org/protobuf-1.30.0
in repository https://gitbox.apache.org/repos/asf/beam.git
discard d83545fe4f2 Bump google.golang.org/protobuf from 1.29.0 to 1.30.0 in
/sdks
add 40bc89da4c7 Revert "Change the type of Samza Runner MaxBundleSize
pipeline option to match with Flink Runner (#25854)" (#25972)
add 111ce402a12 Bump github.com/opencontainers/runc from 1.1.3 to 1.1.5 in
/sdks (#26028)
add 350356f1a5d Bump github.com/tetratelabs/wazero from 1.0.0-rc.1 to
1.0.1 in /sdks (#26024)
add b8e5c70ab9e Bump google.golang.org/api from 0.112.0 to 0.114.0 in
/sdks (#25900)
add 77cc74ddd13 Bump google.golang.org/protobuf from 1.29.0 to 1.30.0 in
/sdks
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 (d83545fe4f2)
\
N -- N -- N
refs/heads/dependabot/go_modules/sdks/google.golang.org/protobuf-1.30.0
(77cc74ddd13)
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:
.../beam/runners/samza/SamzaPipelineOptions.java | 8 +++----
sdks/go.mod | 12 +++++-----
sdks/go.sum | 26 +++++++++++-----------
3 files changed, 23 insertions(+), 23 deletions(-)
