Update CHANGELOG.md using the "Trigger GitHub release" action #9561
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.
We haven't been very good at keeping
CHANGELOG.md
updated (2 days ago I added the changelog for versions 7.2.2-7.2.3 21eb083, and the previus commit was for versions 7.1.3-7.2.1 b60adce).This PR updates the action we use to generate the GitHub release so that it also updates
CHANGELOG.md
(commit author: @babel-bot 😄). Btw, I'm trying to understand how I can test this action which chages the git tree and makes requests to the GH api, but I'm not doing it in this PR since it will take a lot of time to properly set up.