zeekay 9b016bda1a fix(release): the npm publish has shipped nothing since April ...

@hanzo/dev's latest is 0.6.91, published 2026-04-01. Every release run
since has ended red without publishing, for two independent reasons.

1. actions/upload-artifact@v3. The pin carries a comment about
   git.hanzo.ai presenting as GHES, where v4 raises
   GHESNotSupportedError — true, but this file lives under
   .github/workflows/ and therefore runs on github.com, which now
   hard-fails v3 during "Set up job":

     This request has been automatically failed because it uses a
     deprecated version of `actions/upload-artifact: v3`.

   Not one step executed. Two hosts, opposite requirements, one file:
   v3 belongs only under .hanzo/workflows/. Both uploads and the
   download move to v4.

2. Default fail-fast. The aarch64 leg reached the deprecation check
   first and died in 4s, cancelling the other four targets, so
   `release` was skipped entirely. A run that read as one broken
   architecture actually shipped zero. fail-fast: false.

And the packaging loop `continue`s past any artifact it does not
recognise, so a missing target would have quietly produced four npm
packages while @hanzo/dev still named five in optionalDependencies —
users on the fifth arch installing a wrapper with no binary under it.
A new step names the five and refuses before packaging.

Also the nine workspace tests that had preflight red, both stale
against the rename to `dev`:

- bash_completion_uses_code_command_name asserted the literal `_code`,
  a second copy of the product name that went stale the moment
  CLI_COMMAND_NAME became "dev". Derive the expectation from the
  constant so it cannot drift again.

- The seven VT100 snapshots recorded a status header that now includes
  `Directory: <cwd>`, resolved from std::env::current_dir() — the
  checkout path of whoever ran the test. Those snapshots only ever
  matched one machine. The harness now pins cwd to /snapshot: absolute
  so it is taken verbatim, outside $HOME so it is never abbreviated to
  ~/…, and outside any git repo so no Branch: segment appears.

Every architecture stays in the matrix. These are native runners
(ubuntu-24.04-arm, macos-14 for both darwin targets) — no QEMU, so
arm64 costs a runner minute, not emulation.

Verified locally on 1.90.0: 8 passed / 0 failed in
vt100_chatwidget_snapshot, 1 passed / 0 failed for the completion test.

2026-08-06 14:23:32 -07:00

..

src

fix(release): the npm publish has shipped nothing since April

2026-08-06 14:23:32 -07:00

Cargo.toml

dev is ours: the Hanzo Cloud by default, a binary named dev, our namespaces

2026-08-01 14:05:00 -07:00