18fcf0f766
* feat(@shadcn/react): add message-scroller package Add the @shadcn/react headless primitives package with MessageScroller scroll anchoring, streaming follow, history prepend, and jump-to-message behavior. Includes geometry helpers, use-render utility, and unit, browser, and perf tests. * feat(registry): add chat components Add MessageScroller, Message, Bubble, Attachment, and Marker registry sources for base and radix, style variants, preview-03 chat blocks, and registry index wiring. * feat(v4): integrate chat components into docs site Wire chat components into the v4 app with docs routes, example preview pages, message part renderers, markdown support, registry build updates, and supporting lib utilities. * feat(examples): add chat component demos Add base and radix example demos for MessageScroller, Message, Bubble, Attachment, Marker, scroll-fade, and shimmer. * docs: add chat component documentation Add component and utility docs for the chat component set, update docs navigation, and add the June 2026 chat components changelog entry. * chore: regenerate registry JSON output Rebuild public registry artifacts for all style variants with the new chat components. * chore(release): add @shadcn/react publish and CI pipeline Add Changesets prerelease workflow, browser test job, RELEASING docs, and monorepo wiring for publishing @shadcn/react independently from the shadcn CLI. * docs: fix display of component preview on mobile * fix * fix * docs: add message scroller docs * style: format * fix
2.7 KiB
Releasing
This monorepo publishes two packages independently with Changesets:
shadcn— the CLI and tooling.@shadcn/react— headless React primitives.
They version on their own lines. A change to one never bumps the other unless a changeset says so.
1. Add a changeset
Every change that should publish needs a changeset. Run:
pnpm changeset
Select the affected package(s) and bump level. One PR can carry separate changesets for shadcn and @shadcn/react at different levels. A PR with no changeset publishes nothing.
2. Stable release
Stable releases are automated by .github/workflows/release.yml (the release job, on push to main):
- Merged changesets accumulate on
main. - The Changesets action opens/updates a "Version Packages" PR that bumps versions and writes changelogs.
- Merging that PR triggers
changeset publish, which builds all packages (pnpm build:packages) and publishes any whose version is ahead of npm — each to thelatesttag.
pnpm build:packages (turbo run build --filter=./packages/*) builds shadcn and @shadcn/react but never apps/v4.
3. Prereleases (per-PR snapshots)
Add the release: beta or release: rc label to a PR. The prerelease job in release.yml:
- Verifies the branch has changesets (a label on the version PR is a no-op, since it consumed them).
- Runs
changeset version --snapshot <channel>— stamps a unique0.0.0-<channel>-<timestamp>on each changeset'd package. - Builds and runs
changeset publish --tag <channel> --no-git-tag. - Uploads the published package list;
prerelease-comment.ymlposts apnpm dlxinstall line per package and removes the label.
The label selects the dist-tag/channel; the changesets on the branch select which packages publish. Snapshots are timestamped, so they never touch latest and never collide.
# Install a snapshot from the PR comment, e.g.:
pnpm dlx @shadcn/react@0.0.0-beta-20260624120000
4. Prerelease trains (sustained -beta.N / -rc.N)
For a baking release line (e.g. 1.0.0-rc.0, -rc.1, …) rather than throwaway snapshots, use Changesets pre mode:
pnpm changeset pre enter rc # writes .changeset/pre.json
# ...normal changeset + Version PR cycle now produces -rc.N versions on the rc tag...
pnpm changeset pre exit # back to stable; next Version PR ships X.Y.Z on latest
Notes
pnpm-workspace.yamlsetsminimumReleaseAge: 2880(48h), so freshly published stable/beta versions take time to resolve in normal installs. Usepnpm dlx <pkg>@<exact-snapshot-version>to test immediately.- Publishing uses npm OIDC/provenance (
id-token: write+npm@latest); noNPM_TOKENsecret is needed.