@wordbricks/velen 0.2.2-win32-x64 → 0.2.3-darwin-arm64

package/README.md

@@ -42,8 +42,8 @@ Release:
 
 - Keep `apps/cli/package.json` at `0.0.0-dev`.
 - Keep `apps/cli/Cargo.toml` and `apps/cli/Cargo.lock` at `0.0.0` on normal development commits.
-- Before tagging a release, update `apps/cli/Cargo.toml` and `apps/cli/Cargo.lock` to the real release version on the tagged commit.
-- After the release commit, return the Rust workspace version metadata to `0.0.0` on the next development commit.
+- Only temporary `release/...` branches should change `apps/cli/Cargo.toml` and `apps/cli/Cargo.lock` to the real release version before tagging.
+- After the release is tagged, close or delete that temporary release branch/PR so `origin/main` stays at `0.0.0`.
 - Configure npm trusted publishing for `@wordbricks/velen` with GitHub Actions using the workflow filename `cli-release.yml`.
 - Push a tag like `cli-v0.1.0` or `cli-v0.1.0-alpha.1`.
 - The `cli-release` workflow validates `cli-v<version>` against `apps/cli/Cargo.toml`, builds GNU and musl Linux binaries plus the other platform binaries, stages npm tarballs, creates a GitHub release, and publishes them to npm with `npm publish --provenance`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "cpu": [
-    "x64"
+    "arm64"
   ],
   "description": "Velen CLI",
   "files": [
@@ -10,7 +10,7 @@
   "license": "Apache-2.0",
   "name": "@wordbricks/velen",
   "os": [
-    "win32"
+    "darwin"
   ],
   "publishConfig": {
     "access": "public"
@@ -20,7 +20,7 @@
     "url": "git+https://github.com/wordbricks/velen.git",
     "directory": "apps/cli"
   },
-  "version": "0.2.2-win32-x64",
+  "version": "0.2.3-darwin-arm64",
   "engines": {
     "node": ">=18"
   }