Search documentation

Search Stepper docs, API, guides, and release notes.

guides

Changelog

Beta

Latest Stepper registry updates, API changes, examples, and documentation notes.

RSS

Release automation

The changelog is generated by Release Please, while the docs keep the public UI focused on what changed.

Release source
Release Please
Public notes stay in sync with the release workflow without showing numeric release labels in the UI.
Minor releases
feat(...)
Feature commits on main are picked up by Release Please as minor release candidates.
Pending queue
GitHub PRs
Release and dependency PRs stay reviewable before a tag is created.

Open pending pull requests

Release notes

Human-readable notes for the registry component: what changed, why it matters, and how it affects copied source.

May 15, 2026

beta

Beta registry release

The Stepper beta release focuses the public registry on the core primitive, polished docs, and production-ready source ownership.

Added

  • Added public item-level state with useStepperItem for custom composed indicators without duplicating active or completed state.
  • Added a focused beta badge across the docs surface and homepage.

Changed

  • Reworked the docs navigation to keep unfinished examples and recipes marked as soon while the Stepper reference stays prominent.
  • Refined the documentation UI with sharper tabs, quieter scrollbars, cleaner sidebar states, and more consistent navigation buttons.

Registry

  • Bumped the registry component version to the beta channel.
  • Regenerated and verified the flat public shadcn registry artifacts.

May 2, 2026

Registry release candidate

The hardened Stepper registry component became the release candidate, with clearer docs around composition, fallback behavior, and copied-source ownership.

Added

  • Promoted the release-candidate hardening work into the registry channel.
  • Kept the public docs focused on the shadcn registry component instead of package-style distribution.

Docs

  • Aligned the changelog with the release-please workflow.
  • Clarified the path toward final production QA: install from /stepper.json, verify copied source, then publish usage guidance.

Registry

  • Validated that generated public registry artifacts remain up to date after the release bump.
  • Preserved flat registry URLs for shadcn CLI installs and compatibility rewrites.

May 2, 2026

Release candidate hardening

Stepper now catches the common composition mistakes that used to fail silently, while the docs explain the registry-first workflow more directly.

Added

  • Added development warnings for duplicate StepperItem values.
  • Added development warnings when StepperContent points at a missing StepperItem value.
  • Added development warnings when StepperItem is rendered outside StepperList.

Fixed

  • Prevented accidental StepperItem nodes inside StepperContent from changing the real step order.
  • Preserved the StepperContent primitive marker in the generated single-file registry output.

Docs

  • Documented controlled fallback behavior for missing or disabled values.
  • Documented asChild requirements for custom triggers and navigation controls.
  • Clarified that Stepper represents UI state while the app owns validation, routing, and persistence.
  • Reframed recipes with copy-this-when guidance for faster pattern selection.

May 1, 2026

Flat registry URLs

Stepper now serves the shadcn registry from root-level JSON files, which matches the public registry index requirements and keeps the old /r links working.

Fixed

  • Published the registry index at /registry.json and the component item at /stepper.json.
  • Kept /r/registry.json and /r/stepper.json as compatibility rewrites for older links.

Registry

  • Updated the public homepage metadata to the francozeta-stepper.vercel.app domain.
  • Verified the production registry with the shadcn CLI dry run before documenting the URL.

May 1, 2026

MDX docs and shadcn registry infrastructure

This release moved the project into a real documentation and distribution shape: MDX pages, generated registry artifacts, and release automation now live together.

Added

  • Added the MDX documentation site with pages for install, API, examples, forms, patterns, styling, and changelog.
  • Added shadcn registry build output so Stepper can be installed as source code with the shadcn CLI.

Changed

  • Connected the docs status badge to the registry workflow.
  • Documented the registry flow as the primary source-ownership install path.

May 1, 2026

Docs examples and recipe patterns

The docs gained stronger install guidance, product-style examples, and recipes for route-based, mobile, segmented, and compact stepper compositions.

Docs

  • Expanded examples around checkout, onboarding, controlled state, status states, and form wizard flows.
  • Added recipe patterns that keep Stepper focused while the application owns validation, routing, and persistence.

May 1, 2026

Styling guidance

The styling docs clarified how Stepper uses shadcn/ui semantic tokens and data attributes.

Docs

  • Documented the theme tokens that Stepper reads from the host app.
  • Added examples for state selectors and indicator composition.

May 1, 2026

Initial Stepper primitive

The first public release established the composable Stepper primitive, source-generation flow, demos, and docs strategy.

Added

  • Added controlled and uncontrolled state, horizontal and vertical layouts, content panels, navigation helpers, and asChild composition.
  • Added public useStepper helpers plus data attributes for active, completed, disabled, error, and positional styling.
  • Added modular source files with a generated single-file registry artifact for shadcn-style distribution.