@runfile/cli 0.18.0 → 0.20.0

package/bin/darwin-arm64/README.md

@@ -85,6 +85,17 @@ $ run dev --port=4000
 $ run :completions install bash # or zsh, fish, powershell
 ```
 
+**5. Keep it up to date:**
+
+```bash
+$ run :update                     # update to the latest release in place
+$ run :update --version v0.19.0   # or pin a specific release tag
+```
+
+`:update` re-runs the install script for your platform, replacing the binary where it already lives. npm-managed
+installs are handled too: on Linux/macOS `:update` runs `npm install -g @runfile/cli@latest` for you; on Windows it
+prints that command to run from a fresh shell (npm can't overwrite the running `run.exe` there).
+
 ---
 
 ## Why Runfile?

package/bin/darwin-x64/README.md

@@ -85,6 +85,17 @@ $ run dev --port=4000
 $ run :completions install bash # or zsh, fish, powershell
 ```
 
+**5. Keep it up to date:**
+
+```bash
+$ run :update                     # update to the latest release in place
+$ run :update --version v0.19.0   # or pin a specific release tag
+```
+
+`:update` re-runs the install script for your platform, replacing the binary where it already lives. npm-managed
+installs are handled too: on Linux/macOS `:update` runs `npm install -g @runfile/cli@latest` for you; on Windows it
+prints that command to run from a fresh shell (npm can't overwrite the running `run.exe` there).
+
 ---
 
 ## Why Runfile?

package/bin/linux-arm64/README.md

@@ -85,6 +85,17 @@ $ run dev --port=4000
 $ run :completions install bash # or zsh, fish, powershell
 ```
 
+**5. Keep it up to date:**
+
+```bash
+$ run :update                     # update to the latest release in place
+$ run :update --version v0.19.0   # or pin a specific release tag
+```
+
+`:update` re-runs the install script for your platform, replacing the binary where it already lives. npm-managed
+installs are handled too: on Linux/macOS `:update` runs `npm install -g @runfile/cli@latest` for you; on Windows it
+prints that command to run from a fresh shell (npm can't overwrite the running `run.exe` there).
+
 ---
 
 ## Why Runfile?

package/bin/linux-x64/README.md

@@ -85,6 +85,17 @@ $ run dev --port=4000
 $ run :completions install bash # or zsh, fish, powershell
 ```
 
+**5. Keep it up to date:**
+
+```bash
+$ run :update                     # update to the latest release in place
+$ run :update --version v0.19.0   # or pin a specific release tag
+```
+
+`:update` re-runs the install script for your platform, replacing the binary where it already lives. npm-managed
+installs are handled too: on Linux/macOS `:update` runs `npm install -g @runfile/cli@latest` for you; on Windows it
+prints that command to run from a fresh shell (npm can't overwrite the running `run.exe` there).
+
 ---
 
 ## Why Runfile?

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@runfile/cli",
-  "version": "0.18.0",
+  "version": "0.20.0",
   "description": "Runfile CLI — an easy-to-use, batteries-included task runner",
   "repository": "https://github.com/Skiley/runfile",
   "homepage": "https://github.com/Skiley/runfile",