@imfusion/web-ui 0.6.0 → 0.6.1-dev.1.g23386714

package/README.md

@@ -133,7 +133,7 @@ Web UI skill.
 | `/web-ui-dev-design-component`            | Brand design pass for a component that works but isn't styled yet.                                                      |
 | `/web-ui-dev-story`                       | Author or update a Storybook story.                                                                                     |
 | `/web-ui-dev-commit`                      | Commit workflow: changelog skill, staged docs audit, CI-parity checks, house commit format.                             |
-| `/web-ui-dev-release`                     | Prepare release highlights, commit release notes, verify, and create an annotated local tag.                            |
+| `/web-ui-dev-release`                     | Prepare release notes, commit them, and ship the approved release.                                                      |
 | `/web-ui-dev-changelog`                   | Generate and validate the required one-line CHANGELOG.md entry for a web-ui change, including direct commits to master. |
 | `/web-ui-dev-audit-docs`                  | Audit docs against staged or recent changes for staleness, gaps, and drift.                                             |
 | `/web-ui-dev-audit-pass-through-defaults` | Check `@default` annotations on pass-through props against Base UI upstream.                                            |
@@ -184,23 +184,16 @@ npx tsx scripts/version.ts        # prints, changes nothing
 
 ### Cutting a release
 
-The detailed Unreleased entries are the release record. Before cutting a version, add one to three titled `Highlights` blocks
-at the top for people deciding whether to update. Start each with the outcome; include a small usage example or link when it
-helps someone explore the feature. Then prepare the dated release section:
+The release skill prepares the dated release section from detailed Unreleased entries and commits it through the normal
+approval gate. Then ship that prepared commit:
 
 ```bash
-npm run release:prepare -- --version 0.5.1
+npm run release
 ```
 
-Commit that change through `/web-ui-dev-release`, then create the local annotated tag:
-
-```bash
-npm run release:tag -- --version 0.5.1
-```
-
-The tag command requires a clean working tree, runs full verification, and creates `web-ui/v0.5.1`. It never pushes. Push
-that tag only after explicit approval. The tag triggers a build that publishes `0.5.1` as `latest` and repoints the `dev`
-dist-tag at the same version.
+The command reads the prepared version from `CHANGELOG.md`, requires a clean working tree, runs full verification, creates
+`web-ui/v0.5.1`, and pushes the tag. TeamCity builds that tag, publishes `0.5.1` as `latest`, and points `dev` at the same
+version.
 
 The tag name must match `web-ui/vX.Y.Z` exactly. Both the version script's `--match` and the TeamCity branch filter in
 [`.teamcity/settings.kts`](./.teamcity/settings.kts) key off that shape; a tag in any other form publishes nothing.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@imfusion/web-ui",
-  "version": "0.6.0",
+  "version": "0.6.1-dev.1.g23386714",
   "description": "The official Web UI component library for ImFusion web apps",
   "author": "ImFusion GmbH",
   "license": "UNLICENSED",
@@ -77,8 +77,7 @@
     "verify:changelog": "tsx scripts/verify/changelog.ts",
     "verify:staged": "tsx scripts/verify/staged.ts",
     "verify:full": "tsx scripts/verify/full.ts && npm run verify:tests",
-    "release:prepare": "tsx scripts/release.ts prepare",
-    "release:tag": "tsx scripts/release.ts tag",
+    "release": "tsx scripts/release.ts",
     "format": "prettier --write .",
     "lint": "eslint . --cache --fix",
     "lint:inspect": "npx @eslint/config-inspector@latest",