Skip to content

Streamline release tooling: changesets + pkg.pr.new#25

Draft
JReinhold wants to merge 2 commits intostorybookjs:mainfrom
JReinhold:chore/changesets-release-tooling
Draft

Streamline release tooling: changesets + pkg.pr.new#25
JReinhold wants to merge 2 commits intostorybookjs:mainfrom
JReinhold:chore/changesets-release-tooling

Conversation

@JReinhold
Copy link
Copy Markdown

Summary

  • replace auto with Changesets release tooling and Storybook-standard release workflows
  • add pkg.pr.new preview publishing, repo release guidance, and a release changeset
  • minimally adapt CHANGELOG.md for Changesets compatibility without rewriting history

Validation

  • pnpm install
  • pnpm format
  • pnpm build
  • pnpm check:ci

Notes

  • pnpm changeset status --verbose could not be run from this nested checkout because Changesets detects the parent Storybook workspace as the root; the standalone repo configuration and files were updated directly.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@JReinhold JReinhold added the internal Changes only affect the internal API label Apr 8, 2026
@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new bot commented Apr 8, 2026

Open in StackBlitz

npm i https://pkg.pr.new/storybookjs/addon-webpack5-compiler-swc/@storybook/addon-webpack5-compiler-swc@25

commit: 5af3167

Add the ^0.0.0-0 peer dependency range for Storybook packages so
canary releases are accepted.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Changes only affect the internal API

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant