feat(release): guard against commit bodies that release-please cannot parse - #106
Merged
Merged
Conversation
… parse a commit body with markdown headers can fail the conventional-commits parser. when it does, release-please silently drops the commit from its calculation, the release workflow still reports success, and no release pr, tag, or publish results. a release that never happened then looks exactly like a release that was not owed. this adds a hazard brief that records the 2026-09-24 incident, names the safe body shape every prior release-cutting commit used, and gives the tell to check after any feat or fix merge. - records the measured incident and the workflow log line that named the cause - states the safe shape: plain prose plus dash bullets, no markdown headers, lines under 100 - names the recovery: a new parseable feat or fix commit on main - flags the tell: no release pr after feat or fix work means read the release log note on the changelog: this release also covers the grove-reach role work that merged as a67ea47 and was dropped by the parser, so the notes will not name it. Co-authored-by: Ulad Kasach <uladkasach@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feat(release): guard against commit bodies that release-please cannot parse
a commit body with markdown headers can fail the conventional-commits parser. when it does,
release-please silently drops the commit from its calculation, the release workflow still reports
success, and no release pr, tag, or publish results. a release that never happened then looks
exactly like a release that was not owed.
this adds a hazard brief that records the 2026-09-24 incident, names the safe body shape every
prior release-cutting commit used, and gives the tell to check after any feat or fix merge.
note on the changelog: this release also covers the grove-reach role work that merged as a67ea47
and was dropped by the parser, so the notes will not name it.
🐢🌊 surfed in by seaturtle[bot]