Files
dev/codex-cli/scripts
zeekay b39c98c4d4 feat: rebrand npm to @hanzo/dev, wire ZT transport into tunnel protocol
- rust-release.yml: change npm scope from @openai to @hanzo, remove
  openai.com deploy trigger
- build_npm_package.py: rebrand all @openai/codex references to
  @hanzo/dev, rename platform packages (codex-* → hanzo-dev-*)
- stage_npm_packages.py: update tarball naming to match hanzo-dev-npm-*
- cloud.rs: complete ZT wiring — zt:// URLs now authenticate via ZT
  fabric, dial service, create TunnelConnection from channels, spawn
  ZT frame transport, and run standard dispatch loop
- zt/tunnel.rs: add run_zt_transport() — newline-delimited JSON frame
  protocol over ZtConnection (AsyncRead+AsyncWrite) with heartbeat
- Bump hanzo-tunnel dep to v0.1.1 (adds from_channels constructor)
- Add zt-tunnel feature combining zt + tunnel + hanzo-zt/tunnel
2026-03-12 00:33:29 -07:00
..

npm releases

Use the staging helper in the repo root to generate npm tarballs for a release. For example, to stage the CLI, responses proxy, and SDK packages for version 0.6.0:

./scripts/stage_npm_packages.py \
  --release-version 0.6.0 \
  --package codex \
  --package codex-responses-api-proxy \
  --package codex-sdk

This downloads the native artifacts once, hydrates vendor/ for each package, and writes tarballs to dist/npm/.

When --package codex is provided, the staging helper builds the lightweight @openai/codex meta package plus all platform-native @openai/codex variants that are later published under platform-specific dist-tags.

If you need to invoke build_npm_package.py directly, run codex-cli/scripts/install_native_deps.py first and pass --vendor-src pointing to the directory that contains the populated vendor/ tree.