Skip to main content
Smithers 0.33.0 is the rename release. The published npm package is now smthrs; smithers-orchestrator gets no further releases. The CLI binary is still smithers, the product is still Smithers: only the package identifier changed.

Upgrading

This is a breaking change: there is no compatibility alias.
Then update every import specifier, including the workspace scope:
  • smithers-orchestratorsmthrs (and every subpath: smthrs/ui, smthrs/gateway-react, smthrs/gateway-ui, smthrs/jsx-runtime, …)
  • @smithers-orchestrator/*@smthrs/*
  • /** @jsxImportSource smithers-orchestrator *//** @jsxImportSource smthrs */
A one-liner that covers a whole repo (use git grep, not rg: ripgrep silently skips files containing NUL bytes):
bunx smthrs upgrade applies the rename to your project with an agent.

Rename workflows in the pack

The rename itself was executed by two new pack workflows, both included in this release as reusable patterns:
  • rename-package: parallel Codex Luna sweep lanes over disjoint path scopes with a sequential finalize lane (lockfiles, generated bundles, repo checks), with a live lane-status UI.
  • rename-dependents: one lane per dependent repo where a Luna agent clones, renames, and must prove git grep returns zero hits before a Sol reviewer independently re-checks the diff and a draft PR is opened.

Fixes

  • Effect 4 type compatibility: Context.Tag/TagClass references that do not exist in Effect 4 were removed (#1467).
  • Complete Effect 4 runtime compatibility (#1463).
  • README contract tests pin the hero image and drop stale assertions (#1345).
  • apps/cli/src/index.js is executable again.

Upgrade notes

  • Breaking: the npm package name changed from smithers-orchestrator to smthrs, including the @smthrs/* workspace scope. No compat alias is published; pinned installs of smithers-orchestrator keep working but never see another release.
  • The smithers CLI binary name, workflow file formats, database schema, and gateway protocol are unchanged: no data migration is needed.