build: release with changesets - #306
Merged
Merged
Conversation
Adopt the release setup less-loader uses: `.changeset/` with the shared changelog generator, and a Release workflow that lets `changesets/action` either open the version pull request or publish once it lands. `standard-version` goes, and `version` and `release` become `changeset version` and `changeset publish`. `@changesets/get-github-info` is held at `0.8` deliberately: `1.x` replaces the `getInfo` and `getInfoFromPullRequest` the generator formats links from with a differently shaped `getCommitInfo` and `getPullRequestInfo`, so taking it would mean rewriting a file that is otherwise a verbatim copy of less-loader's. Carry a changeset for the merge that main already holds, so the first release off this setup is the 7.0.0 the rename and the new `linters` option call for. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GzZci4NQeiqwdrVfd7dGXy
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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
Adopts the release setup
less-loaderuses, so this repository releases the same way as the rest of them:.changeset/withconfig.json, theREADME.mdboilerplate and the sharedchangelog-generator.mjs— a verbatim copy of less-loader's, withrepopointed atwebpack/lint-webpack-plugin..github/workflows/release.yml, runningchangesets/actionon pushes tomainwith the same pinned action SHAs, so it either opens the version pull request or publishes to npm once that lands. Guarded byif: github.repository == 'webpack/lint-webpack-plugin'.standard-versionis dropped;versionandreleasebecomechangeset versionandnpm run build && changeset publish. TheCHANGELOG.mdheader no longer points at standard-version for commit guidelines.@changesets/get-github-infois pinned to^0.8.0, matching less-loader, and that is deliberate rather than a stale range:1.xreplaces thegetInfo/getInfoFromPullRequestthe generator formats its links from with a differently shapedgetCommitInfo/getPullRequestInfo, so taking it would mean rewriting a file that is otherwise a straight copy.@changesets/cliis on the current^3.0.2.It also carries one changeset for the merge that
mainalready holds, so the first release off this setup is the7.0.0the rename and the newlintersoption call for. Drop or re-level that file if you would rather the renamed package start elsewhere — it is the only thing deciding the next version number.What kind of change does this PR introduce?
build.
Did you add tests for your changes?
No — this is release tooling and touches no source. I verified it by running the pipeline rather than by asserting on it:
npx changeset statusreports the major, andnpm run versionproduced6.0.0→7.0.0with the changelog entry rendered by the custom generator. That dry run was reverted, so the commit carries the un-consumed changeset.Does this PR introduce a breaking change?
No. No source file changes and
peerDependenciesare untouched.If relevant, what needs to be documented once your changes are merged or what have you already documented?
Contributors now add a changeset instead of relying on commit messages for the changelog. Worth a line in the contributing guide if you want it spelled out; the
.changeset/README.mdcovers the basics.Use of AI
Written with Claude Code, driven interactively. I asked for less-loader's setup to be ported here; Claude read that repository, ported the files and verified the pipeline end to end. I reviewed the result.
🤖 Generated with Claude Code
https://claude.ai/code/session_01GzZci4NQeiqwdrVfd7dGXy
Generated by Claude Code