Updating

Installed components are source files you own, so nothing updates behind your back. When you want a newer version, re-run the install with --overwrite.

Check what changed

Every component has a version (shown on its page and at the top of its file) and a changelog. The whole library’s changes are also machine-readable at /r/changelog.json, newest first.

• Patch or minor (1.1.0 → 1.2.0): safe to update; props keep working.
• Major (1.x → 2.0): a prop changed. The changelog entry says what to change.

Update a component

npx shadcn@latest add https://notchset.dev/r/button.json --overwrite

npx shadcn@latest add https://notchset.dev/r/radix-nova/button.json --overwrite

npx shadcn@latest add @notchset-pro/data-table --overwrite

This replaces the component files and the shared files they need, and writes the item's CSS into your global stylesheet again (keep your own overrides in separate rules). If you edited the component, review the diff before committing: your changes are in git, so nothing is lost.

Your AI can do it too

.notchset/AGENTS.md (added with the agent rules item, below) tells agents how to update. Ask: “Update the Notchset components, check the changelog for breaking changes first.”

npx shadcn@latest add https://notchset.dev/r/notchset-ai.json

Pro updates

Pro is one payment, not a subscription: new Pro components and updates are included for as long as Pro is offered (see Pricing). Everything you install is yours and keeps working forever; nothing phones home. Your registry key is only needed to pull Pro items and their updates. See Pro setup.