You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e9b59bf
Browse filesBrowse the repository at this point in the historyBrowse files
test(release): invert the assertion that encoded the tag-stripping defect (#569)
This test computed the strip-cleaned form of the composed message and
asserted the tag body equalled it. That was the right call while the defect
stood - it documented shipped behaviour instead of papering over it - and
it left instructions for this exact moment: if the body ever DOES contain
its heading, the invocation picked up --cleanup=verbatim and the assertion
should be relaxed deliberately rather than chased as a regression.
Now inverted: the composed message must reach the tag object byte-for-byte,
with the version heading and each group heading asserted individually so a
regression names what was lost.
Added a negative control. Every assertion above would pass vacuously on a
message containing no `#` lines, since strip and verbatim agree on such a
message - the fix would be untested and the suite would still be green.
Requiring the two forms to differ proves the fixture exercises the bytes
the defect destroys. That also keeps _git_strip_cleanup load-bearing rather
than leaving it dead behind the inversion.
Verified the assertion discriminates: it passes on a verbatim body and
fails on a default-cleanup body.
CHANGELOG: covered by the 2.11.0 Fixed entry on tag-message stripping
0 commit comments