This is an automated email from the ASF dual-hosted git repository.
git-hulk pushed a change to annotated tag v2.17.0-rc1
in repository https://gitbox.apache.org/repos/asf/kvrocks.git
*** WARNING: tag v2.17.0-rc1 was modified! ***
from 6e0903999 (commit)
to 0c294baa5 (tag)
tagging f21e52a659586c8d29367f37f8f5d6fbe6d28b44 (commit)
replaces v1.3.1
by git-hulk
on Wed Sep 9 14:26:17 2026 +0800
- Log -----------------------------------------------------------------
release: copy for tag v2.17.0-rc1
-----------------------------------------------------------------------
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
annotated tag 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 (6e0903999)
\
N -- N -- N refs/tags/v2.17.0-rc1 (0c294baa5)
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:
tests/gocase/unit/info/info_test.go | 2 --
1 file changed, 2 deletions(-)