chore: start the changelog at this package's first release - #359
Merged
Merged
Conversation
`CHANGELOG.md` carried 290 lines of `eslint-webpack-plugin` releases — 6.0.0 down to 1.0.0, under `standard-version` headings, with compare links into a repository this one was renamed away from. The package is published as `diagnostics-webpack-plugin` and has never released, so none of it describes a version anyone can install under this name. Only the heading is left. `changeset version` keeps line 1 and everything from line 3 on, inserting the release between the two — checked against what it has already generated on `changeset-release/main` — so 1.0.0 will be written under it and nothing else will be there.
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.
Summary
CHANGELOG.mdcarried 290 lines ofeslint-webpack-pluginreleases — 6.0.0 down to 1.0.0, understandard-versionheadings (### [5.0.2],⚠ BREAKING CHANGES) with compare links intowebpack-contrib/eslint-webpack-pluginandwebpack/eslint-webpack-plugin. The package is published asdiagnostics-webpack-pluginand has never released, so none of it describes a version anyone can install under this name. Onchangeset-release/maintoday the generated file is 384 lines: 94 of 1.0.0, then that.Only the heading is left. The generated 1.0.0 entry is what goes under it, and nothing else — that is what this PR is for; it is not written by hand here because the release writes it.
Checked rather than assumed: everything after the generated 1.0.0 section on
changeset-release/mainis today'sCHANGELOG.mdfrom line 3 on, byte for byte. Sochangeset versionkeeps line 1 and the rest of the file and inserts the release between the two — remove the rest and the release's own output is the whole file. #307 regenerates frommainon every push, so it will show that after this merges.The old history stays where it belongs: the
eslint-webpack-pluginreleases, tags and npm package still carry it, and it is in this repository's git history.What kind of change does this PR introduce?
chore.
Did you add tests for your changes?
n/a.
Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
n/a — the README's migration guides are where a reader coming from
eslint-webpack-pluginis served, and they are untouched.Use of AI
AI was used. It compared the release branch's generated changelog against the current file to establish where
changeset versioninserts and what it preserves, then removed what the release does not need.🤖 Generated with Claude Code
https://claude.ai/code/session_01GzZci4NQeiqwdrVfd7dGXy
Generated by Claude Code