infra: Change NEXT_CHANGELOG.md template to exclude next version number#2408
Merged
infra: Change NEXT_CHANGELOG.md template to exclude next version number#2408
NEXT_CHANGELOG.md template to exclude next version number#2408Conversation
…mber Practically speaking, we can't actually guess what this version number is going to be until all the work has been collected together on `dev` and we consider the totality of the changeset and their impact on the version number. Because the previous regular expression in the release script was intentionally fragile, this also makes it less fragile since changing the template would have previously broken it. This won't get us terribly far, but it will at least be a bit more durable. Note, because regex, it's still going to be fragile, but this should give us _some_ runway. :) Follows #2323
bnjjj
approved these changes
Jan 16, 2023
Geal
approved these changes
Jan 17, 2023
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
3 participants
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.
Practically speaking, we can't actually guess what this version number is
going to be until all the work has been collected together on
devand weconsider the totality of the changeset and their impact on the version
number.
Because the previous regular expression in the release script was
intentionally fragile, this also makes it less fragile since changing the
template would have previously broken it. This won't get us terribly far,
but it will at least be a bit more durable. Note, because regex, it's still
going to be fragile, but this should give us some runway. :)
Follows #2323