spinuptui 0.24.0 → 0.24.2

package/CHANGELOG.md

@@ -11,6 +11,31 @@ versions; such changes are called out here.
 
 ## [Unreleased]
 
+## [0.24.2] - 2026-08-06
+
+### Fixed
+- **Crash on toast dismissal: `remove expects a renderable child object`.**
+  `@opentui/core` changed the signature of its internal `remove()` method
+  starting at `0.4.3` (it now requires the renderable object itself, not an
+  id string), and the toast library we depend on hasn't published a release
+  that matches. Our own dependency range (`^0.4.1`) let a fresh install with
+  no lockfile — e.g. a global `bun add -g` on a machine that had never
+  installed spinuptui before — resolve to a broken later patch and crash the
+  first time a toast (PHP upgrade, reboot, cache purge, etc.) tried to
+  dismiss itself. `@opentui/core` and `@opentui/react` are now pinned to the
+  exact last known-good patch (`0.4.2`) until the toast library ships a fix.
+
+## [0.24.1] - 2026-08-06
+
+### Fixed
+- **`bun update -g spinuptui` no longer silently fails to update.** While
+  spinuptui is pre-1.0, a package-manager global install records a caret
+  version range (e.g. `^0.22.2`) that, under semver, only matches patch
+  releases — every later minor release fell outside it, so `update -g`
+  reported success without actually updating anything. The documented and
+  in-app update command (Help/About panel, README) is now
+  `bun add -g spinuptui@latest`, which always pulls the true latest version.
+
 ## [0.24.0] - 2026-07-15
 
 ### Added
@@ -1239,7 +1264,9 @@ Initial tagged release.
 ### Notes
 - Read-only release: works with a SpinupWP **Read Only** API token.
 
-[Unreleased]: https://github.com/mwender/spinupwp-tui/compare/v0.24.0...HEAD
+[Unreleased]: https://github.com/mwender/spinupwp-tui/compare/v0.24.2...HEAD
+[0.24.2]: https://github.com/mwender/spinupwp-tui/compare/v0.24.1...v0.24.2
+[0.24.1]: https://github.com/mwender/spinupwp-tui/compare/v0.24.0...v0.24.1
 [0.24.0]: https://github.com/mwender/spinupwp-tui/compare/v0.23.0...v0.24.0
 [0.23.0]: https://github.com/mwender/spinupwp-tui/compare/v0.22.3...v0.23.0
 [0.22.3]: https://github.com/mwender/spinupwp-tui/compare/v0.22.2...v0.22.3

package/README.md

@@ -150,8 +150,10 @@ bun run build:binary     # produces ./spinuptui — move it onto your PATH
 The app tells you when a newer release exists — a gold `✦ vX.Y.Z` appears next
 to the version in the header (and in the `?` About panel).
 
-- **Package install:** `bun update -g spinuptui` (the About panel shows the
-  same command).
+- **Package install:** `bun add -g spinuptui@latest` (the About panel shows
+  the same command). Don't use `bun update -g` — while spinuptui is pre-1.0,
+  it records a caret range (e.g. `^0.22.2`) that excludes every later minor
+  release, so `update -g` reports success but silently doesn't update.
 - **Source checkout:** press **`u`** in the About panel to update in place
   (`git pull --ff-only`; refuses if you have uncommitted changes, and never
   merges/rebases). It can't hot-reload the already-running process, so it tells

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "spinuptui",
-  "version": "0.24.0",
+  "version": "0.24.2",
   "description": "SpinupTUI — a terminal dashboard for browsing, monitoring, and managing your SpinupWP servers and sites.",
   "type": "module",
   "bin": {
@@ -42,8 +42,8 @@
   "license": "MIT",
   "dependencies": {
     "@opentui-ui/toast": "^0.0.5",
-    "@opentui/core": "^0.4.1",
-    "@opentui/react": "^0.4.1",
+    "@opentui/core": "0.4.2",
+    "@opentui/react": "0.4.2",
     "react": "^19.0.0",
     "socket.io-client": "^4.8.3"
   },

package/src/lib/appUpdate.ts

@@ -139,7 +139,17 @@ export function installChannel(): InstallChannel {
 
 // The one-liner Help shows for a package install (also used by runSelfUpdate's
 // "not a checkout" message so every path names the same command).
-export const PACKAGE_UPDATE_CMD = "bun update -g spinuptui"
+//
+// Deliberately `add ... @latest`, not `update -g`: while spinuptui is pre-1.0,
+// `bun add -g spinuptui` (no version) records a caret range like `^0.22.2`,
+// which per semver only matches 0.22.x. Every minor release (0.23.0, 0.24.0, ...)
+// falls outside that range, so `bun update -g` silently no-ops forever — it
+// re-resolves within the stale range and finds nothing newer. `@latest` bypasses
+// the recorded range entirely and rewrites it to match, so the *next* update
+// hits the same wall until the following minor bump. Verified live against a
+// real stale install (0.22.2 -> 0.24.0): `update -g` exited 0 without updating,
+// `add -g spinuptui@latest` updated correctly.
+export const PACKAGE_UPDATE_CMD = "bun add -g spinuptui@latest"
 
 // The real checkout directory, resolved through Bun's module system rather
 // than process.cwd() — `spinuptui` is typically a global symlink invoked from