Skip to content

Upgrade smithers-orchestrator to smthrs - #1

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

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

Conversation

@roninjin10

Copy link
Copy Markdown

What

The smithers-orchestrator package was renamed on npm to smthrs (and the @smithers-orchestrator/* scope to @smthrs/*), with no compatibility alias published under the old name. This PR migrates svvy from smithers-orchestrator@0.28.0 to smthrs@0.33.0.

Changes

  • Renamed all smithers-orchestrator / @smithers-orchestrator/* references to smthrs / @smthrs/* across the repository (imports, package manifests, docs, workflow definitions).
  • Updated dependency ranges to ^0.33.0 (e.g. smthrs and @smthrs/agents in workflows/package.json).
  • Regenerated lockfiles; they resolve the published smthrs/@smthrs/* 0.33.0 packages with integrity hashes. Regeneration emitted only peer/platform warnings.

Verification

  • git grep smithers-orchestrator is clean (zero matches).
  • The rename and version match the Smithers 0.33.0 changelog; smthrs and @smthrs/agents 0.33.0 are published on npm.
  • Reviewer note from the upgrade pipeline: "Mergeable. The required grep is empty; the 0.33.0 package and scope rename matches the Smithers changelog; smthrs and @smthrs/agents 0.33.0 are published; JSON and diff checks pass; regenerated lockfiles are clean and consistent."

🤖 Generated with Claude Code

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