chore: reconcile release-please with the versions tagged by hand - #23
Merged
Conversation
Its manifest said 0.11.1 while this package ships 0.11.2, because those releases were tagged directly instead of through its pull request. It could not merge without publishing a version that goes backwards, and it would have kept proposing one. The manifest now matches the tags, and the CHANGELOG is backfilled from the notes written when each of those releases was published — not invented after the fact. A changelog that jumps from 0.11.1 to the next version would hide the releases in between, which is worse than a stale one because it reads as complete.
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.
Its manifest said
0.11.1while this package ships0.11.2, because those releases were tagged directly instead of through its pull request. It could not merge without publishing a version that goes backwards.The manifest now matches the tags, and the CHANGELOG is backfilled from the notes written when each release was published — not invented after the fact. A changelog jumping from
0.11.1to the next version would hide the releases in between, which is worse than a stale one because it reads as complete.Greenhouse
evidence/0160.