projmux 0.7.2 → 0.7.3

package/docs/cli.md

@@ -705,18 +705,25 @@ fresh cached update is available, the shell welcome uses Enter=Continue,
 `${XDG_CACHE_HOME:-~/.cache}/projmux/update-skip.json` and suppresses that tag
 until a newer latest release appears.
 
-Installer detection honors
-`PROJMUX_INSTALLER=npm|go|github-release|source`. When unset or invalid,
-the source is reported as `unknown` with guidance to set the variable.
+Installer detection honors an explicit
+`PROJMUX_INSTALLER=npm|go|github-release|source` first. When it is unset,
+detection falls back to inspecting the running binary: an npm install tree
+(`node_modules/@projmux/...`) is reported as `npm`, a `go install …@latest`
+binary in `$GOBIN`/`$GOPATH/bin`/`~/go/bin` as `go`, and a local `go build`
+(`make install`) — which reports a `(devel)` main-module version — as `source`.
+`github-release` installs are indistinguishable from a hand-placed binary and
+still require an explicit `PROJMUX_INSTALLER=github-release`. Anything else is
+reported as `unknown` with guidance.
 `apply` is installer-aware and only runs after explicit user selection.
-For npm installs, it runs `npm update -g projmux` and then
-`projmux tmux apply` unless `--no-apply` is set. For Go installs, it
-delegates to the existing atomic `projmux upgrade` flow. For
-`github-release` installs, it downloads the latest matching
-`projmux_<version>_<goos>_<goarch>.tar.gz` release asset, extracts the
+For npm installs, it runs `npm install -g projmux@latest` (which reliably
+crosses minor/major versions where `npm update -g` does not, and re-resolves
+the per-platform optional dependency) and then `projmux tmux apply` unless
+`--no-apply` is set. For Go installs, it delegates to the existing atomic
+`projmux upgrade` flow. For `github-release` installs, it downloads the latest
+matching `projmux_<version>_<goos>_<goarch>.tar.gz` release asset, extracts the
 binary, atomically replaces the current executable, then applies tmux
 configuration unless `--no-apply` is set. `source` installs report an
-actionable error because they must be updated from the source checkout.
+actionable error to update the checkout with `git pull --ff-only && make install`.
 
 ## upgrade
 
@@ -729,7 +736,7 @@ projmux upgrade [--ref @latest|@<tag>|@<branch>]
 runs `projmux tmux apply` (skipped with `--no-apply`). Reads
 `PROJMUX_PROJDIR` from the calling shell and memoizes the primary entry
 to `~/.config/projmux/projdir`. npm-installed binaries reject this
-command; use `projmux update apply` or `npm update -g projmux` for npm
+command; use `projmux update apply` or `npm install -g projmux@latest` for npm
 installs.
 
 ## welcome

package/docs/upgrading.md

@@ -25,10 +25,18 @@ projmux update apply
 Use `--dry-run` to see the planned action and `--no-apply` to skip reloading
 the live tmux config after the binary changes.
 
-Shell Upgrade invokes only `projmux update apply`. Shell Skip until next stores
-the current latest release tag in `update-skip.json`; the prompt appears again
-when the cached latest tag changes. For `source` and unknown installer sources,
-Upgrade prints guidance and continues shell entry without applying anything.
+Shell Upgrade invokes only `projmux update apply`, then reports success or the
+specific failure inline and continues into the shell either way (a failed
+upgrade is never fatal to shell entry). Shell Skip until next stores the current
+latest release tag in `update-skip.json`; the prompt appears again when the
+cached latest tag changes. For `source` and unknown installer sources, Upgrade
+prints guidance and continues shell entry without applying anything.
+
+The installer is detected from an explicit `PROJMUX_INSTALLER` first, then
+inferred from the running binary when unset (npm install tree → `npm`,
+`go install …@latest` binary in `$GOBIN`/`$GOPATH/bin`/`~/go/bin` → `go`, a
+local `go build`/`make install` `(devel)` binary → `source`). `github-release`
+still requires an explicit `PROJMUX_INSTALLER=github-release`.
 
 ## Behavior Changes
 
@@ -118,12 +126,20 @@ npm install -g projmux
 For npm-managed installs, `projmux update apply` runs:
 
 ```sh
-npm update -g projmux
+npm install -g projmux@latest
 projmux tmux apply
 ```
 
+`npm install -g projmux@latest` is used instead of `npm update -g projmux`
+because `npm update -g` honors the installed semver range and frequently
+refuses to move a global install across a newer minor/major release, leaving it
+stuck on an old version. `install -g …@latest` always fetches the newest
+published release and re-resolves the per-platform optional dependency.
+
 The npm shim sets `PROJMUX_INSTALLER=npm` so projmux can detect this path
-automatically. You can also update manually with `npm update -g projmux`.
+automatically. Even when the shim is bypassed, projmux infers the npm install
+from the binary path (`node_modules/@projmux/...`). You can also update manually
+with `npm install -g projmux@latest`.
 
 ## Go Installs
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projmux",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "tmux project session manager",
   "license": "MIT",
   "homepage": "https://github.com/crevissepartners/projmux#readme",
@@ -28,9 +28,9 @@
     "package:npm:pack": "scripts/package-npm.sh --pack"
   },
   "optionalDependencies": {
-    "@projmux/linux-x64": "0.7.2",
-    "@projmux/linux-arm64": "0.7.2",
-    "@projmux/darwin-x64": "0.7.2",
-    "@projmux/darwin-arm64": "0.7.2"
+    "@projmux/linux-x64": "0.7.3",
+    "@projmux/linux-arm64": "0.7.3",
+    "@projmux/darwin-x64": "0.7.3",
+    "@projmux/darwin-arm64": "0.7.3"
   }
 }