Skip to content

Upgrade smithers-orchestrator to smthrs - #61

Open
roninjin10 wants to merge 1 commit into
evmts:mainfrom
smithersai:upgrade-smthrs
Open

Upgrade smithers-orchestrator to smthrs#61
roninjin10 wants to merge 1 commit into
evmts:mainfrom
smithersai:upgrade-smthrs

Conversation

@roninjin10

Copy link
Copy Markdown
Contributor

What

The smithers-orchestrator package was renamed on npm to smthrs as of 0.33.0, with no compatibility alias. This PR upgrades the workflow tooling from smithers-orchestrator@0.17.0 to smthrs@0.33.0.

Changes

  • workflow/package.json: dependency renamed to smthrs@^0.33.0; workflow/bun.lock regenerated with Bun.
  • All imports and @jsxImportSource pragmas swept: workflow/components/docs-workflow.tsx, workflow/components/workflow.tsx, workflow/run-docs.ts, workflow/smithers.ts, workflow/tsconfig.json.
  • workflow/types/smithers-orchestrator-jsx-runtime.d.ts renamed to smthrs-jsx-runtime.d.ts with its module declaration updated to smthrs/jsx-runtime.

Beyond the rename, no additional API migration was needed for the 0.17.0 → 0.33.0 jump.

Verification

  • git grep smithers-orchestrator is clean (no remaining references).
  • Reviewer note: "Upgrade is mergeable. The legacy package grep is empty, the 0.33.0 rename migration matches the changelog, smthrs@0.33.0 is published, source and JSON are intact, the lockfile installs frozen, and TypeScript checks pass."

🤖 Generated with Claude Code

@vercel

vercel Bot commented Aug 2, 2026

Copy link
Copy Markdown

@roninjin10 is attempting to deploy a commit to the evmts Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant