CyberStrike upgrade fails with "Not Found" (version check uses unpublished unscoped package name)

[demo-zexuan]

Description

cyberstrike upgrade fails with Not Found on 1.1.16 and never reaches the install step.

Installation.latest() builds the version-check URL from the old unscoped package name cyberstrike, which is unpublished on npm (the packument still resolves, but has versions: [] and dist-tags: null). GET https://registry.npmjs.org/cyberstrike/latest therefore returns 404, and its statusText — literally Not Found — is thrown as-is at packages/cyberstrike/src/installation/index.ts:225.

Every other call site already uses the scoped name (upgrade()'s npm/pnpm/bun commands, uninstall.ts, packages/script/src/index.ts:44); this one was missed when the package moved to @cyberstrike-io/cyberstrike.

Worth noting: this throw happens inside latest(), i.e. before Installation.upgrade() and outside the UpgradeFailedError handling in cli/cmd/upgrade.ts, so the CLI only prints Unexpected error, check log file at ... instead of the actual reason.

Fix: fetch(\${registry}/@cyberstrike-io%2Fcyberstrike/${channel}`)— returns 200 withversion: 1.1.16. Including the URL and status in the thrown error would make this kind of failure diagnosable from the log, since res.statusText` alone carries no context.

Steps to reproduce

1. Install from npm: npm i -g @cyberstrike-io/cyberstrike@1.1.16
2. Run cyberstrike upgrade
3. It prints Using method: npm, then Error: Unexpected error, check log file at ...

The 404 can also be confirmed directly:

curl -s -o /dev/null -w '%{http_code}\n' https://registry.npmjs.org/cyberstrike/latest                      # 404
curl -s -o /dev/null -w '%{http_code}\n' https://registry.npmjs.org/@cyberstrike-io%2Fcyberstrike/latest    # 200

Interface

CLI / TUI

CyberStrike version

1.1.16

Operating System

macOS 26.6.2 (arm64)

Terminal

iTerm2

Logs / Screenshots

INFO  2026-09-14T07:26:28 +179ms service=default version=1.1.16 args=["upgrade"] cyberstrike
ERROR 2026-09-14T07:26:30 +2303ms service=default name=Error message=Not Found stack=Error: Not Found
    at <anonymous> (src/installation/index.ts:225:34)
    at processTicksAndRejections (native:7:39) fatal

$ npm i -g @cyberstrike-io/cyberstrike@latest
$ cyberstrike --version
1.1.16
$ npm --version
11.12.1

[demo-zexuan]

Cause confirmed, and the fix is verified locally.

Why it 404s: Installation.latest() builds the npm registry URL from the old unscoped name cyberstrike. That package is unpublished — the registry still serves a packument for it, but with versions: [] and dist-tags: null — so GET https://registry.npmjs.org/cyberstrike/latest returns 404 and its statusText (Not Found) is thrown verbatim. Every other call site already uses the scoped name, so this is the one spot the rename missed.

Fix: query the scoped name, encoded the same way packages/script/src/index.ts:44 already does it.

-      return fetch(`${registry}/cyberstrike/${channel}`)
+      const url = `${registry}/@cyberstrike-io%2Fcyberstrike/${channel}`
+      return fetch(url)
         .then((res) => {
-          if (!res.ok) throw new Error(res.statusText)
+          if (!res.ok) throw new Error(`${res.status} ${res.statusText}: ${url}`)
           return res.json()
         })

The error message change belongs to the fix: statusText on its own carries no context, which is why the original failure only ever showed Not Found with no hint of what was requested. Afterwards the same failure would read 404 Not Found: https://registry.npmjs.org/cyberstrike/latest.

Verification: ran the real latest() path from source, with the defines the shipped binary is built with (CYBERSTRIKE_VERSION=1.1.16, CYBERSTRIKE_CHANNEL=latest):

	result
before	error: Not Found at src/installation/index.ts:225:34 — matches the reported log
after	latest=1.1.16

bun turbo typecheck passes (11/11 packages).