Skip to content

Correct the registry directory status - #14

Merged
mblode merged 1 commit into
mainfrom
claude/registry-directory-status
Aug 18, 2026
Merged

Correct the registry directory status#14
mblode merged 1 commit into
mainfrom
claude/registry-directory-status

Conversation

@mblode

@mblode mblode commented Aug 18, 2026

Copy link
Copy Markdown
Owner

AGENTS.md (and CLAUDE.md, which symlinks to it) said the shadcn directory PR was "open, unmerged". It was closed in Jul 2026, by Matthew rather than a maintainer, after three months with no review and no objection.

It also carried two mistakes worth recording so they don't repeat: the name @blode-ui rather than the actual @blode namespace, and ui.blode.co as the homepage, which is the vanity host that 301s to the canonical path.

What changed

Replaced the stale sentence with the submission history, plus what was measured against the live directory rather than assumed:

  • 280 live entries, every one carrying a logo, author optional
  • entries sort alphabetically, so @blode sits between @blockus and @boldkit
  • registry.json serves 161 items with $schema and no inlined file content, so that requirement passes
  • the "flat registry at the root" requirement is not enforced in practice: neither @7ovr nor @23rd serves a root /registry.json and both are listed

The /r/styles/default/ note is unchanged. It is still the likely objection, and 77 component docs still point at it.

Resubmitted as shadcn-ui/ui#11543. #10340 could not be reopened because its fork had been deleted.


Note

Low Risk
Documentation-only change to agent guidance; no runtime, registry build, or install behavior changes.

Overview
Updates AGENTS.md (and symlinked agent docs) so the Registry directory section matches reality instead of saying a shadcn listing PR is still open.

It drops the stale “open, unmerged” framing and adds submission history for #10340 (closed Jul 2026, wrong @blode-ui / ui.blode.co) and the Aug 2026 resubmit #11543 with @blode and https://blode.co/ui. It also records live-directory checks (280 entries, logo/author norms, alphabetical placement) and tightens review requirements with measured registry facts—161 items, no inlined files content—and notes that a root /registry.json is not consistently enforced among listed registries.

The /r/styles/default/ mirror warning is unchanged.

Reviewed by Cursor Bugbot for commit c3d9d98. Bugbot is set up for automated code reviews on this repo. Configure here.

This file said the shadcn directory PR was "open, unmerged". It was closed in
Jul 2026, by Matthew rather than a maintainer, and it drew no review and no
objection in the three months it was open. It also carried two mistakes: the
name `@blode-ui` rather than the actual `@blode` namespace, and `ui.blode.co`
as the homepage, which is the vanity host that 301s to the canonical path.

Replaced with the submission history, since the standing claim here has now been
wrong twice, plus what was actually measured against the live directory in Aug
2026: 280 entries, every one with a `logo`, alphabetically sorted.

Two of the listed requirements were checked rather than assumed. `registry.json`
serves 161 items with `$schema` and no inlined file content, so that one passes.
The "flat registry at the root" requirement is not enforced in practice: neither
`@7ovr` nor `@23rd` serves a root `/registry.json` and both are listed.

The `/r/styles/default/` note stands unchanged; it is still the likely objection.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Aug 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
blode-ui Error Error Aug 18, 2026 10:56pm

Request Review

@mblode
mblode marked this pull request as ready for review August 18, 2026 23:47
@mblode
mblode merged commit 8998649 into main Aug 18, 2026
1 of 2 checks passed
@mblode
mblode deleted the claude/registry-directory-status branch August 18, 2026 23:47
@cursor

cursor Bot commented Aug 18, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_3ae403fe-1147-454b-94b8-d2cfee668da7)

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.

1 participant