This is an automated email from the ASF dual-hosted git repository.

git-hulk pushed a change to branch 2.17
in repository https://gitbox.apache.org/repos/asf/kvrocks.git


 discard f661ad0f6 test(info): remove orphaned version assertion comment
 discard d30b9c69c test(info): remove unstable version assertion
 discard 6e0903999 fix(ci): use approved action revisions in nightly workflow
 discard fc47355b4 release: prepare source release apache-kvrocks-2.17.0
     add 450d1734a fix(ci): use approved action revisions in nightly workflow
     add 93ae824b4 test(info): remove unstable version assertion
     add bbb136f49 test(info): remove orphaned version assertion comment
     add f21e52a65 release: prepare source release apache-kvrocks-2.17.0

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   (f661ad0f6)
            \
             N -- N -- N   refs/heads/2.17 (f21e52a65)

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:

Reply via email to