Registry - Migrate to registry V3 - #2611
Open
SpicyPete wants to merge 24 commits into
Open
Conversation
SpicyPete
requested review from
datamali and
sago2k8
and removed request for
a team
August 21, 2026 21:43
Contributor
🚨 Registry drift detectedApp:
Components needing attention
Generated by lookout audit-changes. |
The lint job runs `bun run lint` and fails on a dirty tree. `bun install` reprints yarn.lock (bunfig `[install.lockfile] print = "yarn"`), and the committed mirror no longer matched what bun 1.4.0 prints from the current bun.lock, so the job failed with " M frontend/yarn.lock". The stale copy came from c97ee60, where the yarn.lock regenerated alongside the clipboard-polyfill addition had loose ranges (framer-motion@>=4.0.0, react-hook-form@^7.0.0, date-fns@2.x, acorn@^8, browserslist@>= 4.21.0, @chakra-ui/styled-system@>=2.0.0, @tanstack/router-core@^1.170.0) filed under the opposite duplicate-version entry, plus a split semver@^7.5.4 entry. No dependency, version, or integrity hash changes -- only range-key grouping. Verified byte-identical across four warm runs and a cold install with no node_modules, and the printed output covers both darwin and linux optional binaries, so it is platform-independent and will match CI. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Diffed all 163 vendored files against the published registry (https://redpanda-ui-registry.netlify.app/r/{name}.json). 162 were already byte-identical; only sidebar.tsx was behind. SidebarInset gains min-w-0 so wide content scrolls its own container instead of the document. Resynced from the published content rather than hand-patched, so the file stays byte-identical to upstream. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Commit 88c16c7 ("lock file") committed a yarn.lock whose peer-range specifier groupings (@chakra-ui/styled-system, @tanstack/router-core, acorn, browserslist, date-fns, framer-motion, react-hook-form) do not match what bun 1.4.0 generates, so `bun install` in CI rewrote the file and the lint job's dirty-tree check failed. Regenerated from package.json + bun.lock with the pinned bun 1.4.0. Result is byte-identical to the lockfile at 28ee6ac, the last commit on this branch with a green lint job. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Bumps @base-ui/react ^1.5.0 -> ^1.7.0 (with its @base-ui/utils and
@floating-ui/* subtree) and re-pulls all 90 vendored registry items.
8 of 163 vendored files changed; the other 155 were already at 3.1.0:
- progress: drop the translateX indicator: Base UI already sizes the fill
with an inline width, so the percentage was applied twice.
- radio-group: keep an explicitly-passed `value` controlled while form
state initializes (react-hook-form hands over undefined on first render).
- toggle-group: support group-level `disabled`, inherited by items.
- tabs: forward Base UI's `activateOnFocus` on TabsList.
- auto-form boolean/select/oneof: alignItemWithTrigger={false} on
SelectContent.
- theme.css: drop the now-unused caret-blink keyframe (Base UI 1.7's OTP
Field owns the caret; console does not vendor input-otp).
No callsite changes required. The lockfile delta is confined to the
base-ui subtree — @base-ui/utils no longer needs its nested reselect pin.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Comment on lines
+28
to
+30
| # Pinned: bun generates yarn.lock (bunfig print = "yarn") and the output | ||
| # changes between bun versions, which trips the lint job's dirty-tree check. | ||
| bun-version-file: frontend/.bun-version |
|
|
||
| - The removed-token sweep is empty across `src` **and** `tests`, and no removed name reappears. | ||
| - Every `[upstream]` local addition is re-applied; every non-item triaged. | ||
| - `bun run theme:check && bun run type:check && bun run lint && bun run build && bun run test`. |
Contributor
There was a problem hiding this comment.
I like the theme check being a distinct command
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade redpanda-ui registry to v3
Re-pulls
src/components/redpanda-ui/from the v3 registry and migrates the app ontothe new token and variant APIs.
Registry pull
--color-*names to 162. Removed tokens compile tonothing (no build error), so every retired name was swept out of
srcandtests.Badgemoves to the two-axistone+variantAPI,Button'sinverse-outline/inverse-ghost→current-*, plusAlert,DropdownMenuandSheetupdates.text-gray-*,bg-gray-*, …) replaced with semantic tokensrather than re-pinned — under v3 they fall through to Tailwind's palette and change hue.
New guardrail
bun run theme:check(wired intobun run build) audits a palette override sheetagainst the registry's token surface: fails on dead token names and on
half-overridden families, where a control takes your colour at rest and the
registry's on hover.
Fixes and cleanup
*border reset hardened inglobals.cssso Tailwindborder-*utilities paint again;@source not "../.claude"keeps class names inthe agent skill docs out of the bundle.
the shadowlink schema-registry section.
cnfast→clsx(upstream change);tailwind-mergeconfig now stops aleading-*being dropped by an adjacent font size.src/colors.ts,state/type-experiments.ts, registrylib/shared-types.tsandlib/use-copy.tsx.Docs
registry-upgrade.md(the pull-and-migrate procedure and itssilent-failure traps) and
style-use-tokens.md;ui-developmentSKILL.md andstyle-use-variants.mdupdated for the v3 variant tables.Note for reviewers
Console is embedded in cloud-ui and both apps declare tokens on the same
:root, sothis needs to land alongside the matching cloud-ui registry bump — otherwise the
host's palette wins for whichever app is behind.