chore: reset legacy changelogs for nx release#98
Merged
lukascivil merged 2 commits intomasterfrom Apr 24, 2026
Merged
Conversation
lukascivil
changed the title
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
1 participant
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.
Objective
Clear the pre-existing,
@jscutlery/semver-generated entries from the two library CHANGELOG files so the newnx releasepipeline (introduced in #97) starts from a clean slate on the next version bump.What was done
libs/json-difference/CHANGELOG.md(removed 160 lines of legacy entries).libs/json-difference-cli/CHANGELOG.md(removed 179 lines of legacy entries).nx releasecan append freshly generated sections on top.Test plan
yarn release:dry-runand confirmnx releaseproduces well-formed CHANGELOG sections starting from the current versions.@jscutlery/semverheader survives).