You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@magpie.apache.org by po...@apache.org on 2026/10/15 23:48:06 UTC

(magpie) branch perf/release-mgmt-4-promote-announce updated (5ef33b66 -> 26b7cd6b)

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

potiuk pushed a change to branch perf/release-mgmt-4-promote-announce
in repository https://gitbox.apache.org/repos/asf/magpie.git


 discard 5ef33b66 fix(release-promote, release-announce-draft): emit the right S3 move and gate render on the verdict
 discard 2e151d13 perf(release-promote, release-announce-draft): render the promotion and announcement as code
 discard 802dade9 fix(release-vote-draft, release-vote-tally): fail closed on incomplete input and scan the whole public text
 discard f139fe4b perf(release-vote-draft, release-vote-tally): render the vote drafts and decide the tally as code
 discard 4a1af88f fix(release-verify-rc): run Step 7 as documented and stop false PASS / SKIP / FAIL
 discard 294211f3 perf(release-verify-rc): classify RAT, JVM, Nexus and reproducibility results as code
 discard cefefcd2 fix(release-rc-cut): fail closed where the rendered commands and record could mislead
     add 7881cb4d fix(release-rc-cut): fail closed where the rendered commands and record could mislead
     add 75f1ffd0 perf(release-verify-rc): classify RAT, JVM, Nexus and reproducibility results as code
     add 090c0325 fix(release-verify-rc): run Step 7 as documented and stop false PASS / SKIP / FAIL
     add b9c9d70a perf(release-vote-draft, release-vote-tally): render the vote drafts and decide the tally as code
     add c17a9c3e fix(release-vote-draft, release-vote-tally): fail closed on incomplete input and scan the whole public text
     add e42d00a5 perf(release-promote, release-announce-draft): render the promotion and announcement as code
     add 26b7cd6b fix(release-promote, release-announce-draft): emit the right S3 move and gate render on the verdict

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   (5ef33b66)
            \
             N -- N -- N   refs/heads/perf/release-mgmt-4-promote-announce (26b7cd6b)

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:
 tools/release-management/tests/test_rc_cut.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)