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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the previously merged candidate #202 has run its cut job,
release-v2.0.18already points at that earlier merge: the parent is already version 2.0.18, while.github/workflows/release-candidate.ymldefines each merged candidate as creatingrelease-vX.Y.Z. Reusing this heading therefore either makes the second cut collide with the existing branch or leaves that branch before #203 even though this changelog now includes it. Advance to a new version, or update and settle the existing release branch instead of opening another v2.0.18 candidate.Useful? React with 👍 / 👎.