Skip to content

feat(registry): add Wensity#10676

Merged
shadcn merged 1 commit into
shadcn-ui:mainfrom
ksparth12:add-wensity-registry
May 18, 2026
Merged

feat(registry): add Wensity#10676
shadcn merged 1 commit into
shadcn-ui:mainfrom
ksparth12:add-wensity-registry

Conversation

@ksparth12
Copy link
Copy Markdown
Contributor

Adds the @wensity community registry to the public registry index.\n\nRegistry: https://github.com/ksparth12/wensity-shadcn-registry\nHomepage: https://wensity.com\nURL template: https://raw.githubusercontent.com/ksparth12/wensity-shadcn-registry/main/{name}.json\n\nThe public registry contains only free Wensity components. Pro components are intentionally excluded and remain available through Wensity's authenticated CLI.\n\nValidation run:\n- pnpm registry:build\n- pnpm validate:registries

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 16, 2026

@ksparth12 is attempting to deploy a commit to the shadcn-pro Team on Vercel.

A member of the Team first needs to authorize it.

@shadcn
Copy link
Copy Markdown
Collaborator

shadcn commented May 18, 2026

hmmm still blocked on non-signed commits. can you try force push?

@ksparth12 ksparth12 force-pushed the add-wensity-registry branch from ba15073 to 1485e91 Compare May 18, 2026 15:33
@ksparth12
Copy link
Copy Markdown
Contributor Author

Force-pushed the branch from current main with a single signed commit. The old unsigned commit is gone and the Signed commits check is passing now.

@shadcn shadcn merged commit 93cde61 into shadcn-ui:main May 18, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants