Release v1.0.5

Overview

This release adds lib/registry-theme.ts to the registry flow and moves registry theme tokens out of globals.css.
Registry components that rely on shared theme variables now ship with their own local theme helper, which makes installs more portable and predictable across projects.

What changed

• Added lib/registry-theme.ts
• Updated registry components to use registryTheme instead of relying on app-level globals.css
• Updated the registry build so generated registry artifacts automatically include lib/registry-theme.ts when required
• Improved installation/docs behavior so helper files are surfaced more clearly

Why this matters

Before this change, some installed registry components depended on theme values defined in globals.css.

Now:

• registry components are more self-contained
• theme tokens travel with the installed component
• portaled UI pieces such as popovers, dialogs, tooltips, dropdowns, and similar components are less likely to fall back to missing global variables
• installs through npx shadcn@latest add @iconiq/<component> behave more reliably across different apps

Installation behavior

When a component needs registry theme tokens, the generated install now also includes:
lib/registry-theme.ts
So imports like:

import { registryTheme } from "@/lib/registry-theme";

are satisfied automatically after install.

Notes

• This is not intended as a breaking change
• Existing local installs can keep working as-is, but newer installs will now receive the helper file automatically
• Registry output and generated JSON files were rebuilt to reflect the new helper-based theme flow

Internal improvements

• Registry build pipeline now detects and bundles lib/registry-theme.ts
• Registry docs/manual install views better reflect generated helper files