@towa-digital/storyblok-nuxt-cv 0.1.2 → 0.1.3

package/README.md

@@ -166,11 +166,13 @@ npm run release       # local: lint + test + build + changelogen + npm publish
 
 CI and releases run on **Buddy** and are **managed in Buddy** (GUI/API), not
 from a committed file — same as `@towa-digital/storyblok-nuxt-sitemap`. Two
-pipelines: *Test* (runs on branch pushes) and *Release to npm* (triggered by
-pushing a **tag** = version, publishes to public npm via
-`npm version $BUDDY_RUN_TAG`).
-
-Release flow: `npx changelogen --release --push` bumps the version + changelog
-and pushes a tag; the tag push triggers the pipeline. Publish auth comes from a
-Buddy **FILE variable** named `npmrc` (npm auth config) on the project or
-workspace — `$npmrc` resolves to its path, copied to `.npmrc` before publish.
+pipelines: *Test* (auto-runs on branch pushes) and *Release to npm*
+(**manual/click-to-run** from `main`, publishes the `package.json` version to
+public npm).
+
+Release flow: bump the version + changelog on `main` (`npx changelogen
+--release` or edit `package.json`), push, then click **Run** on the *Release to
+npm* pipeline in Buddy. Publish auth comes from a Buddy **FILE variable** named
+`npmrc` (npm auth config) on the project or workspace — `$npmrc` resolves to its
+path, copied to `.npmrc` before publish. Publishing requires the version to be
+new (npm rejects re-publishing an existing version).

package/dist/module.json

@@ -4,7 +4,7 @@
   "compatibility": {
     "nuxt": ">=3.10.0"
   },
-  "version": "0.1.2",
+  "version": "0.1.3",
   "builder": {
     "@nuxt/module-builder": "1.0.2",
     "unbuild": "3.6.1"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@towa-digital/storyblok-nuxt-cv",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Keeps Storyblok published content fresh on long-running Nuxt servers by bridging the live cache version (cv) to the render client — no redeploy after publish.",
   "repository": "github:towa-digital/storyblok-nuxt-cv",
   "author": {