@webflare/ui 0.1.0 → 0.1.1

package/README.md

@@ -206,14 +206,14 @@ Publish the root package only. The GitHub Action uses [npm trusted publishing](h
 
 `prepublishOnly` runs `bun run build`. The Action already builds and tests with Bun, then runs `npm publish --ignore-scripts` so that script does not rebuild. `bun publish` cannot authenticate with OIDC.
 
-The Action runs on a published GitHub Release or a manual start, and only from the tag `v<version>` that matches `package.json`.
+The Action runs on a published GitHub Release or a manual start, and only from the tag `<version>` that matches `package.json`. Tags have no `v` prefix.
 
 ### First publish (0.1.0)
 
 Trusted publishing can only be attached to a package that already exists, so 0.1.0 is published by hand.
 
 1. `npm login` in a browser session (interactive 2FA). Do not create a bypass-2FA granular token.
-2. Tag `v0.1.0` on the release commit, then from a clean checkout of that tag:
+2. Tag `0.1.0` on the release commit, then from a clean checkout of that tag:
 
 ```bash
 bun install --frozen-lockfile
@@ -222,7 +222,7 @@ bun run test
 npm publish --access public --ignore-scripts
 ```
 
-3. Do not create a GitHub Release for 0.1.0. It would start the Action, which fails because the version is already on npm.
+3. The GitHub Release uses tag `0.1.0` on the published commit `8ac428b`. Publishing it runs the workflow stored on that commit, which still expects a `v` prefix and would publish again. Disable **Publish to npm** before publishing the release, then enable it again.
 4. On npmjs.com → `@webflare/ui` → Settings → Trusted Publisher → GitHub Actions:
    - Organization or user: `webflare-sh`
    - Repository: `ui`
@@ -232,4 +232,4 @@ npm publish --access public --ignore-scripts
 
 ### Later publishes
 
-Bump the version in all four `package.json` files and run `bun run changelog`. It adds the entry generated from the previous release tag. Run it from a full clone: in a shallow clone it stops with git's error and asks for `git fetch --unshallow --tags`. After the pull request is merged, tag `v<version>` on `master` and publish a GitHub Release for that tag (or start the **Publish to npm** Action from the tag). After the first OIDC publish succeeds, you can set the package to require 2FA and disallow tokens.
+Bump the version in all four `package.json` files and run `bun run changelog`. It adds the entry generated from the previous `X.Y.Z` release tag. Run it from a full clone: in a shallow clone it stops with git's error and asks for `git fetch --unshallow --tags`. After the pull request is merged, tag `<version>` on `master` and publish a GitHub Release for that tag (or start the **Publish to npm** Action from the tag). After the first OIDC publish succeeds, you can set the package to require 2FA and disallow tokens.

package/dist/nuxt/module.json

@@ -1,7 +1,7 @@
 {
   "name": "@webflare/ui",
   "configKey": "wfUi",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "builder": {
     "@nuxt/module-builder": "1.0.3",
     "unbuild": "unknown"

package/dist/panda/lib.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "name": "@webflare/ui",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "panda": "^2.4.0",
   "preset": "./preset.mjs",
   "buildInfo": "./buildinfo.json",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webflare/ui",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Webflare design system: Panda CSS preset, Vue components, and Nuxt module",
   "license": "MIT",
   "author": "Webflare OÜ",
@@ -141,7 +141,7 @@
     "eslint-plugin-unused-imports": "^4.4.1",
     "nuxt": "^4.6.3",
     "reka-ui": "^2.11.0",
-    "typescript": "^5.9.3",
+    "typescript": "~6.0.3",
     "@vitejs/plugin-vue": "^6.0.10",
     "ajv": "^8.20.0",
     "vite": "^8.2.1",
@@ -155,7 +155,7 @@
     "reka-ui": "^2.11.0",
     "nuxt": "^4.6.3",
     "@nuxt/kit": "^4.6.3",
-    "typescript": "^5.9.3"
+    "typescript": "^5.9.3 || ^6.0.0"
   },
   "dependencies": {
     "@pandacss/preset-base": "^2.4.0"