paseo-plugin-machine-status 0.2.3 → 0.3.1

package/OVERVIEW.md

@@ -14,7 +14,7 @@ Machine Status shows what the daemon's Mac is doing while your agents work: CPU
 
 ## Setup
 
-- A macOS daemon on Paseo 0.8 to 0.13. On other platforms the screen says it cannot collect metrics.
+- A macOS daemon on Paseo 0.11 to 0.14. On other platforms the screen says it cannot collect metrics.
 - Docker Desktop, OrbStack or Rancher Desktop for the Docker tab. Without one, the tab says which is missing.
 
 ## What it can change

package/README.md

@@ -1,3 +1,5 @@
+<p align="center"><img src="assets/icon.png" width="88" alt=""></p>
+
 <h1 align="center">paseo-plugin-machine-status</h1>
 
 <p align="center">
@@ -9,7 +11,7 @@
 <p align="center">
   <a href="https://github.com/dutchakdev/paseo-plugin-machine-status/actions/workflows/ci.yml"><img src="https://github.com/dutchakdev/paseo-plugin-machine-status/actions/workflows/ci.yml/badge.svg?branch=main" alt="CI"></a>
   <a href="https://www.npmjs.com/package/paseo-plugin-machine-status"><img src="https://img.shields.io/npm/v/paseo-plugin-machine-status" alt="npm"></a>
-  <img src="https://img.shields.io/badge/Paseo-0.8.x%20%E2%80%93%200.13.x-3987e5" alt="Supports Paseo 0.8.x through 0.13.x, including betas">
+  <img src="https://img.shields.io/badge/Paseo-0.11.x%20%E2%80%93%200.14.x-3987e5" alt="Supports Paseo 0.11.x through 0.14.x, including betas">
   <img src="https://img.shields.io/badge/macOS-only-9aa1a6" alt="macOS only">
   <img src="https://img.shields.io/badge/dependencies-none-c98500" alt="No runtime dependencies">
   <img src="https://img.shields.io/badge/license-MIT-9aa1a6" alt="MIT licensed">
@@ -34,19 +36,22 @@ source that matches your Paseo:
 | Paseo | Source | Command |
 | ----- | ------ | ------- |
 | 0.11 and newer | [Plugin directory](https://paseo.sh/plugins), the reviewed version | `paseo plugin add dutchakdev/machine-status` |
-| 0.9 and newer | npm, the newest release before the directory approves it | `paseo plugin install npm:paseo-plugin-machine-status` |
-| 0.8 | GitHub | `paseo plugin add dutchakdev/paseo-plugin-machine-status` |
+| 0.11 and newer | npm, the newest release before the directory approves it | `paseo plugin install npm:paseo-plugin-machine-status` |
+| 0.8 to 0.10, 0.11.0 betas | GitHub, release 0.2.3, the last one for these versions | `paseo plugin add dutchakdev/paseo-plugin-machine-status --ref v0.2.3` |
 
 `paseo plugin ls` should then show `machine-status` as `running`, and
 `paseo plugin update machine-status` pulls later releases from the same source. From
 Paseo 0.11 a bare `owner/name` names a directory entry, so a GitHub source there needs
 the `git:` prefix: `git:dutchakdev/paseo-plugin-machine-status`.
 
-The plugin supports **Paseo 0.8.x through 0.13.x, including betas**, on both the
+The plugin supports **Paseo 0.11.x through 0.14.x, including betas**, on both the
 daemon, which runs its collectors, and the app, which runs its screens.
 
-The manifest remains `>=0.8.0`, which already admits 0.9.x through 0.13.x. Paseo also checks a
-prerelease's stable version core, so `0.13.0-beta.1` satisfies this range; see
+The manifest asks for `>=0.11.0` because it declares the icon shown in the plugin
+directory, and Paseo 0.8 to 0.10 refuse a manifest with a field they do not know.
+Paseo also checks a prerelease's stable version core, so `0.14.0-beta.1` satisfies
+this range. The 0.11.0 betas pass that check but predate the `icon` field, so they
+refuse the manifest as well and need the release named in the install table; see
 [version requirements](https://paseo.sh/docs/plugins/reference#requirements).
 
 To work on it locally instead:
@@ -360,13 +365,16 @@ including a refusal to terminate the test runner itself.
 ### Paseo versions
 
 The SDK stays pinned to 0.8.0 for typechecking and tests, so the compiler proves
-the plugin uses only the oldest supported API. Paseo supplies the runtime instances
-on every supported release line, so none of it ships with the plugin.
+the plugin uses only the 0.8 API, which every supported release still provides.
+Paseo supplies the runtime instances on every supported release line, so none of
+it ships with the plugin.
 
 Paseo 0.11 replaced surfaces with screens and kept the old calls as deprecated
-aliases. The manifest still admits 0.8, and each connected app evaluates the client
-entry against its own version, so `client/compat.tsx` describes the 0.11 additions
-locally and calls them only after checking that the app has them:
+aliases. Up to 0.2.3 the manifest admitted 0.8, and each connected app evaluates the
+client entry against its own version, so `client/compat.tsx` describes the 0.11
+additions locally and calls them only after checking that the app has them. Since the
+manifest asks for 0.11, every app that loads the plugin takes the first row; the
+fallback stays in the code until it is removed on its own:
 
 | App version | Screen | Sidebar | Opens with | Tab shortcuts in ⌘K |
 | ----------- | ------ | ------- | ---------- | ------------------- |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "paseo-plugin-machine-status",
-  "version": "0.2.3",
+  "version": "0.3.1",
   "description": "Machine dashboard, open ports and Docker control inside Paseo",
   "license": "MIT",
   "author": "dutchakdev",
@@ -43,6 +43,7 @@
   "files": [
     "paseo-plugin.json",
     "OVERVIEW.md",
+    "assets/icon.png",
     "index.client.tsx",
     "index.server.ts",
     "client/",

package/paseo-plugin.json

@@ -1,4 +1,5 @@
 {
   "id": "machine-status",
-  "requirements": { "paseo": ">=0.8.0" }
+  "icon": "assets/icon.png",
+  "requirements": { "paseo": ">=0.11.0" }
 }