opscope 0.5.0 → 0.6.0

package/README.md

@@ -8,7 +8,7 @@ npx opscope link            # skip the menu; any widget name works
 npx opscope@latest link     # pin to latest, or @0.3.0, etc.
 ```
 
-That is the launcher: a menu of the fifteen widgets, or name one and skip
+That is the launcher: a menu of the fourteen widgets, or name one and skip
 it. Only `opscope` is installed as a command; the other binaries stay beside
 it, so `pr` and `link` never replace the coreutils commands of the same
 name. The binaries it starts are the ones attached to the GitHub release of
@@ -17,9 +17,9 @@ commit and date.
 
 ## Platforms
 
-Linux x86_64 (glibc 2.35 or newer), macOS Apple Silicon, and macOS Intel.
-Windows, Alpine/musl, 32-bit, Linux arm64 and an older glibc fail at
-install with a sentence saying so.
+- Linux x86_64 (glibc 2.35 or newer)
+- macOS Apple Silicon
+- macOS Intel
 
 The launcher is a thin package. Each platform is an optional dependency
 npm installs only when `os` / `cpu` / `libc` match, so a Mac never

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opscope",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "Sci-fi terminal widgets that show only real data.",
   "bin": {
     "opscope": "bin/opscope"
@@ -9,9 +9,9 @@
     "postinstall": "node postinstall.js"
   },
   "optionalDependencies": {
-    "opscope-linux-x64": "0.5.0",
-    "opscope-darwin-arm64": "0.5.0",
-    "opscope-darwin-x64": "0.5.0"
+    "opscope-linux-x64": "0.6.0",
+    "opscope-darwin-arm64": "0.6.0",
+    "opscope-darwin-x64": "0.6.0"
   },
   "files": [
     "bin",

package/platform.js

@@ -25,10 +25,10 @@ const path = require('path');
 const LAUNCHER = 'opscope';
 
 // One row per artefact the release workflow actually produces. A
-// platform that is only a wish is not a row: Alpine, Windows and
-// Linux arm64 fail at install because they are absent here, which is
-// the sentence the issue asked for rather than a package that
-// installs and then cannot run.
+// platform that is only a wish is not a row: anything absent here
+// fails at install with a sentence saying what is published, which is
+// what the issue asked for rather than a package that installs and
+// then cannot run.
 //
 // `os` / `cpu` / `libc` are npm's own selectors. npm installs only
 // the optionalDependency whose selectors match and skips the rest,
@@ -85,7 +85,7 @@ function glibcTooOld(h) {
 }
 
 // Every binary, read from the manifest rather than restated.
-// A restated list is how a fifteenth widget ships in the tarball and
+// A restated list is how a new widget ships in the tarball and
 // not in the npm package, and the launcher then cannot launch it.
 // `[[bin]]` is the same list `opscope` already asserts against.
 function binsFromManifest(repoRoot) {
@@ -199,7 +199,6 @@ function unsupportedMessage(h) {
     'It publishes:',
     publishedPlatforms(),
     '',
-    'Windows, Alpine/musl, 32-bit and Linux arm64 are not published.',
     'Build from source: https://github.com/stealth-factory/opscope',
   ].join('\n');
 }