Repository navigation
build(release): give perf commits their own changelog section - #227
Merged
Merged
Conversation
csemver.toml kept csemver's default hidden state for perf, so performance changes never reached CHANGELOG.md: the 0.25.0 range's construction buffer reuse and projected row sizing did not render. perf commits now render under "Performance Improvements". Closes #226
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
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.
Closes #226.
perf commits kept csemver's default hidden state, so performance changes never reached CHANGELOG.md. They now render under "Performance Improvements".
csemver --dry-run --release-as 0.25.0shows the section with #222 (construction buffer reuse) and #208 (MAX_EMITS row sizing); every other section is unchanged (22 breaking, 11 features, 20 fixes, 2 refactors).