astralkit 0.3.0 → 0.3.1

package/CHANGELOG.md

@@ -0,0 +1,37 @@
+# Changelog
+
+All notable changes to the `astralkit` SDK package.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.3.1] — 2026-04-18
+
+### Added
+- `peerDependencies` declaration: `tailwindcss >= 3.0.0`. Installing `astralkit` in a project without Tailwind now surfaces a clear peer-dep warning instead of silent breakage.
+- File header comment on `astralkit-theme.css` explicitly marks it as the Tailwind v3 legacy file. Points readers at the `astralkit/theme-v3` export path and explains the v4 alternative.
+
+### Fixed
+- No functional changes from `0.3.0` — this is a metadata + documentation patch.
+
+## [0.3.0] — 2026-04-18
+
+### Changed (breaking behavior fix)
+- **`astralkit/theme` export now resolves to the Tailwind v4 file (`astralkit-theme-v4.css`).** Previously it pointed at `astralkit-theme.css` (the v3 `:root {}` file), which meant Tailwind v4 users were loading tokens that weren't registered with Tailwind's `@theme` system. Utilities like `bg-ak-primary` and `text-ak-text` were only working because the separate `astralkit-utilities.css` contains its own `@theme` blocks; the theme import was effectively dead weight.
+  - If you were relying on `@import "astralkit/theme"` resolving to the v3 `:root` syntax (e.g., in a Tailwind v3 project), import `astralkit/theme-v3` explicitly instead.
+  - If you're on Tailwind v4, no action needed — the new default is what you should have been getting all along.
+
+### Added
+- New `astralkit/theme-v3` export — explicit path to the Tailwind v3 legacy file (`astralkit-theme.css`).
+- `astralkit/theme-v4` export retained (unchanged) — still points at the v4 file. Existing imports keep working.
+- v4 theme refinements across 12 commits of token architecture work (including rail/panel elevated color overrides, sidebar token tuning, avatar size/badge tokens, and Phase A token standardization).
+- `primitives/.npmignore` — excludes `*.backup` and `*.pre-v4-split` scratch files from published tarballs. The `0.3.0` release removed ~220 kB of v3-migration scratch that was accidentally shipping in earlier versions.
+
+### Fixed
+- Tailwind v3 plugin registration (via CLI init) now covers additional `plugins: [...]` formatting variants.
+
+## [0.2.0] — 2026-04-02
+
+### Added
+- Initial public release on npm.
+- Design tokens (theme CSS), utilities CSS, palette presets, primitives folder, `cn()` helper, Tailwind v3/v4 configs.

package/astralkit-theme.css

@@ -1,6 +1,12 @@
 :root {
   /* ══════════════════════════════════════════════════════════
-     AstralKit Design Tokens (Tailwind v3)
+     AstralKit Design Tokens — Tailwind v3 (LEGACY)
+
+     Imported via `astralkit/theme-v3`. For new projects on
+     Tailwind v4, use `astralkit/theme` (which resolves to the
+     @theme-based v4 file). This file uses :root CSS variables
+     because Tailwind v3 doesn't support the @theme directive.
+
      Default: Black & white neutral theme.
      Override any variable in your own :root block to brand it.
      ══════════════════════════════════════════════════════════ */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "astralkit",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Design tokens and component primitives for accessible UI — Tailwind CSS v4",
   "type": "module",
   "exports": {
@@ -25,12 +25,21 @@
     "ai-rules.md",
     "lib/",
     "LICENSE",
-    "README.md"
+    "README.md",
+    "CHANGELOG.md"
   ],
   "dependencies": {
     "clsx": "^2.1.0",
     "tailwind-merge": "^2.2.0"
   },
+  "peerDependencies": {
+    "tailwindcss": ">=3.0.0"
+  },
+  "peerDependenciesMeta": {
+    "tailwindcss": {
+      "optional": false
+    }
+  },
   "keywords": ["astralkit", "design-tokens", "tailwind", "css", "ui"],
   "homepage": "https://astralkit.com",
   "repository": {