From 5848fbe1bf21df26c644ae5620de05aaaad74265 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Fri, 10 Jul 2026 16:42:39 +0000
Subject: [PATCH] chore: version packages

---
 .changeset/thick-donuts-relax.md | 7 -------
 packages/cli/CHANGELOG.md        | 8 ++++++++
 packages/cli/package.json        | 2 +-
 3 files changed, 9 insertions(+), 8 deletions(-)
 delete mode 100644 .changeset/thick-donuts-relax.md

diff --git a/.changeset/thick-donuts-relax.md b/.changeset/thick-donuts-relax.md
deleted file mode 100644
index 8d1f047b..00000000
--- a/.changeset/thick-donuts-relax.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@sanring/cli": minor
----
-
-`init` now writes `src/sanring-theme.css` — the full set of `--sanring-*` design tokens every component reads (color scales, semantic colors, radius, progress/badge tokens). Previously these variables only existed inside the docs app itself, so a fresh `sanring init` + `sanring add` produced components with no visible styling. Existing files are left alone by default (protects any brand-color edits); pass `-f/--force` to reset to the shipped defaults. Also adds the `--sanring-primary`/`--sanring-primary-fg` alias needed for Radio and Checkbox's Tailwind-bridged `bg-primary`/`text-primary`/`border-primary` utilities to resolve.
-
-New `sanring diff [components...]` command. Sanring UI has no version concept — components are copied source, not npm packages — so there was previously no way to know if a local file had drifted from the registry before `add --force` overwrote it. `diff` compares installed components and `sanring-theme.css` against the current registry line by line, printing what's been customized locally versus what changed upstream. Omit component names to check everything currently installed.
diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md
index 4855fc8c..14131efc 100644
--- a/packages/cli/CHANGELOG.md
+++ b/packages/cli/CHANGELOG.md
@@ -1,5 +1,13 @@
 # @sanring/cli
 
+## 0.6.0
+
+### Minor Changes
+
+- 205c89d: `init` now writes `src/sanring-theme.css` — the full set of `--sanring-*` design tokens every component reads (color scales, semantic colors, radius, progress/badge tokens). Previously these variables only existed inside the docs app itself, so a fresh `sanring init` + `sanring add` produced components with no visible styling. Existing files are left alone by default (protects any brand-color edits); pass `-f/--force` to reset to the shipped defaults. Also adds the `--sanring-primary`/`--sanring-primary-fg` alias needed for Radio and Checkbox's Tailwind-bridged `bg-primary`/`text-primary`/`border-primary` utilities to resolve.
+
+  New `sanring diff [components...]` command. Sanring UI has no version concept — components are copied source, not npm packages — so there was previously no way to know if a local file had drifted from the registry before `add --force` overwrote it. `diff` compares installed components and `sanring-theme.css` against the current registry line by line, printing what's been customized locally versus what changed upstream. Omit component names to check everything currently installed.
+
 ## 0.5.1
 
 ### Patch Changes
diff --git a/packages/cli/package.json b/packages/cli/package.json
index dc6bb49c..b106266d 100644
--- a/packages/cli/package.json
+++ b/packages/cli/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@sanring/cli",
-  "version": "0.5.1",
+  "version": "0.6.0",
   "description": "CLI for adding Sanring UI components to your Angular project",
   "license": "MIT",
   "type": "module",