This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.bouncycastle-bcprov-jdk18on-1.78
in repository https://gitbox.apache.org/repos/asf/tez.git
discard f1c70c4bd Bump org.bouncycastle:bcprov-jdk18on from 1.77 to 1.78
add 66a6ca64b TEZ-4552. Upgrade protobuf to 3.24.4 due to CVE. (#345)
(Shilun Fan reviewed by Laszlo Bodor)
add 7a9211e4d TEZ-4559: Fix Retry logic in case of Recovery (#353).
(Laszlo Bodor, reviewed by Ayush Saxena)
add b81166ed5 Bump org.bouncycastle:bcprov-jdk18on from 1.77 to 1.78
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 (f1c70c4bd)
\
N -- N -- N
refs/heads/dependabot/maven/org.bouncycastle-bcprov-jdk18on-1.78 (b81166ed5)
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:
pom.xml | 2 +-
.../main/java/org/apache/tez/dag/api/client/DAGClientImpl.java | 10 ++++++++--
.../java/org/apache/tez/dag/api/client/rpc/TestDAGClient.java | 1 +
3 files changed, 10 insertions(+), 3 deletions(-)
