Repository navigation
ci: release through changesets and drop the npm shim - #233
Conversation
Remove the `.github/shims/npm` wrapper that rewrote `npm publish` to `npm stage publish`, and replace the `standard-version` based `release` script with changesets so the release workflow publishes via `npm run release`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #233 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 3 3
Lines 18 18
Branches 2 2
=========================================
Hits 18 18 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe release configuration now uses Changesets scripts for package versioning and publishing. The workflow calls those scripts. The npm publish shim and its Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to
|
Summary
Finishes moving releases onto changesets so new versions are cut automatically by the GitHub release workflow:
.github/shims/npm(the wrapper that rewrotenpm publishtonpm stage publish) and the workflow step that put it onPATH.standard-versionbasedreleasescript withchangeset publish, and addschangesetandversion-packages(changeset version) scripts.standard-versionis removed from devDependencies.release.ymlnow callsnpm run version-packages/npm run releasethroughchangesets/action, still authenticating via the npm trusted publisher (OIDC).Release flow: PRs include a changeset (
npx changeset) → on merge tomainthe workflow opens/updates the "chore(release): new release" PR → merging that publishes to npm and creates the tag and GitHub release.Note: without the shim, releases publish directly instead of being staged.
5.0.1(#230) is not on npm or tagged yet, so the first run after this merges will publish it.What kind of change does this PR introduce?
ci
Did you add tests for your changes?
No, release tooling only.
npm run lintpasses.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?
Contributors should add a changeset (
npx changeset) to PRs that need a release.Use of AI
Changes were made with Claude Code (Claude Opus 5.5) under my direction and reviewed by me; it edited the workflow,
package.json, and lockfile, and ran lint locally.🤖 Generated with Claude Code
Summary by CodeRabbit