This is an automated email from the ASF dual-hosted git repository.
xuba pushed a change to branch
dependabot/maven/amoro-shade-zookeeper-3/org.apache.zookeeper-zookeeper-3.9.2
in repository https://gitbox.apache.org/repos/asf/amoro-shade.git
omit 475c2bf Update zookeeper.version to 3.9.3
omit 9c9275d Merge branch 'main' into
dependabot/maven/amoro-shade-zookeeper-3/org.apache.zookeeper-zookeeper-3.9.2
omit c2e7e16 Bump org.apache.zookeeper:zookeeper in
/amoro-shade-zookeeper-3
add e7fcdf4 (hotfix) bump actions/setup-java version to fix cache error
(#11)
add 35f0bf5 Bump org.apache.zookeeper:zookeeper in
/amoro-shade-zookeeper-3
add fcd1d27 Update zookeeper.version to 3.9.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 (475c2bf)
\
N -- N -- N
refs/heads/dependabot/maven/amoro-shade-zookeeper-3/org.apache.zookeeper-zookeeper-3.9.2
(fcd1d27)
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:
.github/workflows/ci.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
