@dynomate/cli 0.0.21 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,10 +1,12 @@
1
1
  # @dynomate/cli
2
2
 
3
- This package installs the native Dynomate command-line client. Test releases use
4
- the npm `next` tag:
3
+ This package installs the native Dynomate command-line client. For current
4
+ installation and download instructions, see
5
+ [Dynomate CLI installation](https://dynomate.io/docs/cli/installation/).
6
+ Test releases use the npm `next` tag:
5
7
 
6
8
  ```bash
7
- npm install --global --allow-scripts=@dynomate/cli @dynomate/cli@next
9
+ npm install --global --ignore-scripts=false --allow-scripts=@dynomate/cli @dynomate/cli@next
8
10
  dynomate-cli --version
9
11
  ```
10
12
 
@@ -18,44 +20,23 @@ Run the same install command again to upgrade. The package exposes only
18
20
  - 64-bit GNU/Linux (`x64`) with glibc 2.35 or newer (Ubuntu 22.04 baseline)
19
21
  - 64-bit Windows (`x64`)
20
22
 
21
- Installation downloads the archive for the current platform from the immutable
22
- release at
23
- `https://releases.dynomate.io/cli/dynomate-cli-v<version>/`. Before trusting an
24
- archive hash, the installer verifies that release's detached `manifest.sig`
23
+ Installation downloads the archive for the current platform from an immutable
24
+ Dynomate release. Before trusting an archive hash, the installer verifies that
25
+ release's detached `manifest.sig`
25
26
  over the exact `manifest.json` bytes with the public key packaged in this npm
26
27
  package. It validates the authenticated target, filename, size, and SHA-256,
27
28
  then atomically installs only the `dynomate-cli` executable.
28
29
 
29
30
  Install scripts are required. npm 12 blocks dependency lifecycle scripts unless
30
- they are explicitly approved, and other npm configurations can also skip them.
31
- If the native executable is missing, the launcher exits with status 1, performs
32
- no network request, and prints the exact repair command shown above. The
33
- installer needs HTTPS access to `releases.dynomate.io` during installation.
34
-
35
- If npm install scripts cannot run, use a versioned direct installer. On macOS
36
- or GNU/Linux:
37
-
38
- ```bash
39
- curl --fail --silent --show-error --location \
40
- https://releases.dynomate.io/cli/install.sh \
41
- | sh -s -- --version 0.0.21
42
- ```
43
-
44
- On Windows PowerShell:
45
-
46
- ```powershell
47
- & ([scriptblock]::Create(
48
- (Invoke-RestMethod https://releases.dynomate.io/cli/install.ps1)
49
- )) -Version 0.0.21
50
- ```
51
-
52
- Both direct installers authenticate the signed manifest before selecting an
53
- archive. They do not route through npm. The immutable release objects are:
54
-
55
- - [macOS Apple Silicon](https://releases.dynomate.io/cli/dynomate-cli-v0.0.21/dynomate-cli-v0.0.21-aarch64-apple-darwin.tar.gz)
56
- - [macOS Intel](https://releases.dynomate.io/cli/dynomate-cli-v0.0.21/dynomate-cli-v0.0.21-x86_64-apple-darwin.tar.gz)
57
- - [GNU/Linux x64](https://releases.dynomate.io/cli/dynomate-cli-v0.0.21/dynomate-cli-v0.0.21-x86_64-unknown-linux-gnu.tar.gz)
58
- - [Windows x64](https://releases.dynomate.io/cli/dynomate-cli-v0.0.21/dynomate-cli-v0.0.21-x86_64-pc-windows-msvc.zip)
31
+ they are explicitly approved. A saved `ignore-scripts=true` setting also skips
32
+ them unless it is overridden for this install. If the native executable is
33
+ missing, the launcher exits with status 1, performs no network request, and
34
+ points to the installation guide. The installer needs HTTPS access to the
35
+ Dynomate release service during installation.
36
+
37
+ For other installation methods, use the
38
+ [CLI installation guide](https://dynomate.io/docs/cli/installation/). The release
39
+ host is used by the installer to fetch authenticated native archives.
59
40
 
60
41
  Test releases stay on the npm `next` dist-tag. A release operator promotes a
61
42
  validated version to `latest` only after the native release and npm package
package/lib/launcher.js CHANGED
@@ -8,7 +8,7 @@ export async function ensureNativeBinary(binary = nativeBinaryPath()) {
8
8
  await access(binary, process.platform === "win32" ? constants.F_OK : constants.X_OK);
9
9
  } catch {
10
10
  throw new Error(
11
- "The native Dynomate CLI installation is incomplete. npm may not have run this package's install script. Repair it with: npm install --global --allow-scripts=@dynomate/cli @dynomate/cli@next",
11
+ "The native Dynomate CLI installation is incomplete. npm may not have run this package's install script. See https://dynomate.io/docs/cli/installation/ for installation and repair instructions.",
12
12
  );
13
13
  }
14
14
  return binary;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dynomate/cli",
3
- "version": "0.0.21",
3
+ "version": "0.2.0",
4
4
  "description": "Installer and launcher for the native Dynomate CLI",
5
5
  "type": "module",
6
6
  "license": "UNLICENSED",
@@ -8,7 +8,7 @@
8
8
  "type": "git",
9
9
  "url": "https://github.com/dynomate/dynomate-cli"
10
10
  },
11
- "homepage": "https://dynomate.io",
11
+ "homepage": "https://dynomate.io/docs/cli/installation/",
12
12
  "bugs": {
13
13
  "url": "https://github.com/dynomate/dynomate-cli/issues"
14
14
  },