Packages: Ensure changelog entries are attributed to the correct release #33590
Conversation
This file contains 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
gziolo
added
[Type] Developer Documentation
gziolo
requested review from
ajitbohra,
chrisvanpatten,
mkaz,
nerrad and
ntwb
as code owners
sarayourfriend
pushed a commit
that referenced
this pull request
Jul 26, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
After publishing to npm a new version of WordPress packages based on Gutenberg 11.1 plugin release, I went through all commits that happened after that date to check how many PRs were merged afterward. I found out that 5 changelog entries are wrongly located inside the sections for the version that was published today. This PR fixes all that.
In the future, we should consider doing npm publishing on the day of RC1 for the plugin that would completely void this issue.