mirror of https://github.com/hanzoai/bot.git synced 2026-10-30 17:24:26 +00:00

Files

T

zeekay acaeda400a Eradicate OpenClaw — resolve merge conflicts and finish the rebrand

Three coordinated things:

1. Resolve the committed upstream/main merge conflicts. 94 files were
   sitting with raw <<<<<<< HEAD ... >>>>>>> upstream/main blocks. Every
   conflict had HanzoBot/Bot on HEAD and OpenClaw on upstream. Resolved
   by keeping HEAD everywhere — 540 conflict blocks.

2. Rewrite remaining OpenClaw text refs.
     OPENCLAW   → HANZO_BOT
     OpenClaw   → HanzoBot          (PascalCase type identifiers)
     openclaw   → bot               (codebase convention — botToken,
                                    botUsername etc.; avoids invalid
                                    hyphenated JS identifiers)
     openclaw[_]/openclaw[A-Z] → bot[_]/bot[A-Z]   (compound)
     ai.openclaw.x → ai.hanzo.bot.x  (JVM package path)

3. Delete or rename openclaw-named file paths (116 of them). Dead
   duplicates with a Bot-named canonical from the partial migration:
   deleted. Otherwise renamed.
     ai/openclaw/**           → deleted (ai/hanzo/bot/** canonical)
     Sources/OpenClaw*/       → deleted (Sources/Bot* canonical)
     Tests/OpenClawIPCTests/  → deleted (Tests/BotIPCTests canonical)
     OpenClawKit/             → deleted (BotKit canonical)
     openclaw-tools.*.ts      → deleted (bot-tools.*.ts canonical)
     openclaw-root.ts etc.    → deleted (bot-root.ts canonical)
     types.openclaw.ts        → deleted (types.bot.ts canonical)
     extensions/*/openclaw.plugin.json → renamed hanzo-bot.plugin.json
     docs/start/openclaw.md   → renamed hanzo-bot.md (+ zh-CN)
     docs/assets/openclaw-*.png, whatsapp-openclaw*.jpg → deleted
     scripts/.../openclaw-*   → deleted (bot/hanzo-bot parallels)
     openclaw.mjs             → deleted (hanzo-bot.mjs is package.bin)

Then patched 65 broken JS/TS import strings where hanzo-bot had ended
up inside an import path ('./types.hanzo-bot.js' → './types.bot.js'
etc., since the on-disk filename uses the brand-neutral bot- prefix).

Pre-existing lint debt cleaned up to get oxlint --type-aware to 0/0:
removed the dead i18n test that referenced a path no longer existing;
defined the missing DIDConfig and WalletConfig types in types.base.ts
(they were imported but never declared); dropped unused imports;
collapsed redundant type assertion and a tautological meta.bot lookup
that the openclaw→bot rename made redundant.

The a2ui.bundle.js generated artifact is kept at its pre-rebrand
contents — it gets regenerated by 'pnpm canvas:a2ui:bundle' from
sources I cannot rebuild in this commit; the source side is clean.

Verified: 0 occurrences of openclaw (case-insensitive) in tree source
content, 0 file or directory paths with openclaw in the name; oxlint
--type-aware src test reports 0/0.

2026-05-11 17:56:29 -07:00

2.5 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

Stable, beta, and dev channels: semantics, switching, and tagging

You want to switch between stable/beta/dev

You are tagging or publishing prereleases

Development Channels

Development channels

Last updated: 2026-01-21

HanzoBot ships three update channels:

stable: npm dist-tag latest.
beta: npm dist-tag beta (builds under test).
dev: moving head of main (git). npm dist-tag: dev (when published).

We ship builds to beta, test them, then promote a vetted build to latest without changing the version number — dist-tags are the source of truth for npm installs.

Switching channels

Git checkout:

hanzo-bot update --channel stable
hanzo-bot update --channel beta
hanzo-bot update --channel dev

stable/beta check out the latest matching tag (often the same tag).
dev switches to main and rebases on the upstream.

npm/pnpm global install:

hanzo-bot update --channel stable
hanzo-bot update --channel beta
hanzo-bot update --channel dev

This updates via the corresponding npm dist-tag (latest, beta, dev).

When you explicitly switch channels with --channel, HanzoBot also aligns the install method:

dev ensures a git checkout (default ~/hanzo-bot, override with BOT_GIT_DIR), updates it, and installs the global CLI from that checkout.
stable/beta installs from npm using the matching dist-tag.

Tip: if you want stable + dev in parallel, keep two clones and point your gateway at the stable one.

Plugins and channels

When you switch channels with hanzo-bot update, HanzoBot also syncs plugin sources:

dev prefers bundled plugins from the git checkout.
stable and beta restore npm-installed plugin packages.

Tagging best practices

Tag releases you want git checkouts to land on (vYYYY.M.D for stable, vYYYY.M.D-beta.N for beta).
vYYYY.M.D.beta.N is also recognized for compatibility, but prefer -beta.N.
Legacy vYYYY.M.D-<patch> tags are still recognized as stable (non-beta).
Keep tags immutable: never move or reuse a tag.
npm dist-tags remain the source of truth for npm installs:
- latest → stable
- beta → candidate build
- dev → main snapshot (optional)

macOS app availability

Beta and dev builds may not include a macOS app release. That’s OK:

The git tag and npm dist-tag can still be published.
Call out “no macOS build for this beta” in release notes or changelog.

2.5 KiB Raw Permalink Blame History Unescape Escape