Communicate that patches are informational#1164
Merged
Merged
Conversation
Replace the bare "list of all patches" intro with an explanation that patches are informational and require no per-patch action beyond bumping the version. Apply the same wording to the release template so future releases inherit it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ajwild
changed the title
dfreier
approved these changes
Jun 18, 2026
Contributor
|
🎉 This PR is included in version 1.150.8 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
3 participants
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.
What & why
Part of splitting up #1156.
The
## Patchessection opened with "Here is a list of all patches after the release has been announced", which reads like the reader needs to act on each patch. Patches are informational — keeping current on the latest patch version is enough.Replaces that intro with an explanation of the contract, and applies the same wording to
_release-template.mdso future releases inherit it.Targets
maindirectly; independent of the AI-parsable reformat PRs (#1161 / #1162) and the typo-fixes PR (#1163). Usesfix()so semantic-release ships a patch on merge.🤖 Generated with Claude Code