@astrale-os/cli 1.0.0-beta.43 → 1.0.0-beta.44

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/CHANGELOG.md CHANGED
@@ -1,5 +1,12 @@
1
1
  # Changelog
2
2
 
3
+ ## [1.0.0-beta.44](https://github.com/astrale-os/cli/compare/cli/v1.0.0-beta.43...cli/v1.0.0-beta.44) (2026-08-28)
4
+
5
+
6
+ ### Bug Fixes
7
+
8
+ * **update:** pin the public npm registry ([#252](https://github.com/astrale-os/cli/issues/252)) ([b2c766a](https://github.com/astrale-os/cli/commit/b2c766a135789f7507fbbb729e5564b28898e19a))
9
+
3
10
  ## [1.0.0-beta.43](https://github.com/astrale-os/cli/compare/cli/v1.0.0-beta.42...cli/v1.0.0-beta.43) (2026-08-28)
4
11
 
5
12
 
package/README.md CHANGED
@@ -7,12 +7,13 @@
7
7
  ## Installation
8
8
 
9
9
  ```bash
10
- npm install -g @astrale-os/cli@beta
10
+ npm --@astrale-os:registry=https://registry.npmjs.org install -g @astrale-os/cli@beta
11
11
  ```
12
12
 
13
- The npm package is the primary consumer installation. It requires Node.js 22
14
- or newer and installs one bundled `astrale` executable without exposing the SDK
15
- or Kernel package graph at runtime.
13
+ The npm package is the primary consumer installation. The explicit scoped
14
+ registry keeps a project-local private-package registry from shadowing the
15
+ public CLI. It requires Node.js 22 or newer and installs one bundled `astrale`
16
+ executable without exposing the SDK or Kernel package graph at runtime.
16
17
 
17
18
  The standalone binary remains available when installing Node is undesirable:
18
19
 
@@ -111,7 +112,7 @@ An npm-installed CLI never overwrites its own package-manager files. It reports
111
112
  the exact package-manager command instead:
112
113
 
113
114
  ```bash
114
- npm install -g @astrale-os/cli@beta
115
+ npm --@astrale-os:registry=https://registry.npmjs.org install -g @astrale-os/cli@beta
115
116
  ```
116
117
 
117
118
  On ordinary interactive launches, Astrale checks for CLI updates at most once
package/dist/astrale.js CHANGED
@@ -2578,7 +2578,7 @@ var package_default;
2578
2578
  var init_package = __esm(() => {
2579
2579
  package_default = {
2580
2580
  name: "@astrale-os/cli",
2581
- version: "1.0.0-beta.43",
2581
+ version: "1.0.0-beta.44",
2582
2582
  description: "Astrale CLI — connect to existing Astrale kernels",
2583
2583
  keywords: [
2584
2584
  "astrale",
@@ -71173,7 +71173,7 @@ function detectUpdateExecution() {
71173
71173
  function packageManagedInstallCommand(input) {
71174
71174
  const channel = input.channel ?? DEFAULT_UPDATE_CHANNEL;
71175
71175
  const selector = input.version ?? (channel === "stable" ? "latest" : channel);
71176
- return `npm install -g @astrale-os/cli@${selector}`;
71176
+ return `npm --@astrale-os:registry=https://registry.npmjs.org install -g @astrale-os/cli@${selector}`;
71177
71177
  }
71178
71178
  function packageManagedUpdateError(executable, command) {
71179
71179
  return new AstraleError("UPDATE_PACKAGE_MANAGED", "This Astrale installation is owned by a package manager and cannot replace itself.", `Active runtime: ${executable}. Upgrade the public npm installation with: ${command}`);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@astrale-os/cli",
3
- "version": "1.0.0-beta.43",
3
+ "version": "1.0.0-beta.44",
4
4
  "description": "Astrale CLI — connect to existing Astrale kernels",
5
5
  "keywords": [
6
6
  "astrale",