chore: version the merged dependency updates - #32
Merged
Conversation
Every merged change to a public repository is versioned in full, including dependency updates. The CHANGELOG lists what actually landed since the last release rather than a summary written after the fact. Co-Authored-By: Claude Opus 5 <[email protected]>
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.
Zieht die Versionierung der bereits gemergten Dependency-Updates nach.
Nach der Versionierungsregel wird jede gemergte Änderung vollständig versioniert, auch reine Dependency-Updates: Patch-Bump in allen Dateien, die eine Version tragen, CHANGELOG-Eintrag, Tag und Release. Tag und Release folgen nach dem Merge, weil beide auf dem gemergten Stand sitzen müssen.
Der CHANGELOG-Eintrag listet die tatsächlich gemergten Commits statt einer nachträglich formulierten Zusammenfassung.