Skip to content

feat: Update wizard to 0.42.0 - #639

Merged
razor-x merged 1 commit into
mainfrom
fix/update-wizard-0.42.0
Aug 28, 2026
Merged

feat: Update wizard to 0.42.0#639
razor-x merged 1 commit into
mainfrom
fix/update-wizard-0.42.0

Conversation

@chmaltsp

@chmaltsp chmaltsp commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Problem

@seamapi/cli declares the wizard as an optional dependency:

"optionalDependencies": {
  "@seamapi/wizard": "^0.38.1"
}

npm's caret operator only permits patch-level changes for versions below 1.0.0, so ^0.38.1 resolves to >=0.38.1 <0.39.0.

@seamapi/wizard is published at 0.42.0, which falls outside that range. Anyone running npx @seamapi/cli wizard gets a wizard four minor versions stale, and no warning is printed.

Fix

Move the range to ^0.42.0 and refresh the lockfile — the same shape as #637 (^0.28.0^0.38.1).

The dependency stays optional, which is deliberate: packaging sources that disallow non-commercial licenses (the Claude SDK) omit it, and runWizard already handles that with a dedicated UsageError.

Lockfile note for reviewers

The lockfile diff is deliberately minimal — 5 insertions, 5 deletions: the range, plus the wizard's version / resolved / integrity. No other entry is added or removed.

Two traps worth recording, since both silently produce a lockfile that breaks CI:

  1. Registry. A contributor with @seamapi:registry=https://npm.pkg.github.com/ in ~/.npmrc (common for Seam employees) gets a lockfile whose wizard resolved URL points at GitHub Packages. CI's npm ci cannot authenticate there, and because the dependency is optional the failure is swallowed — surfacing later as TS2307: Cannot find module '@seamapi/wizard' rather than an install error. Regenerate with --@seamapi:registry=https://registry.npmjs.org/.
  2. npm version. Regenerating with an npm older than the pinned packageManager (npm@11.19.0) drops the wizard's optional peer subtree — ink, react, @anthropic-ai/sdk, @modelcontextprotocol/sdk, express, hono — 11 entries in total.

This branch was regenerated with npm@11.19.0 against the public registry, and its package set is identical to main's.

Verification

  • npm ci with GitHub auth removed installs the wizard at 0.42.0 with ink/react present.
  • npm run typecheck — clean, on Node 22 and 24 in CI.
  • npm run lint — clean, Prettier included.
  • Full CI green.

Follow-up worth considering

Because a caret cannot cross a minor below 1.0.0, this range goes stale again on the wizard's next minor release. Options: widen to >=0.38.1 <1, or add an explicit Dependabot rule so the bump is automated rather than manual.

🤖 Generated with Claude Code

@chmaltsp
chmaltsp requested a review from razor-x as a code owner August 27, 2026 22:50
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

The optional dependency was pinned at `^0.38.1`. Because npm's caret
operator only permits patch-level changes below 1.0.0, that range
resolves to `>=0.38.1 <0.39.0`, so `npx @seamapi/cli wizard` installed a
wizard four minor versions behind the published 0.42.0.

Lockfile regenerated with the pinned npm@11.19.0 so the wizard's
optional peer subtree (ink, react, and their peers) is preserved.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@chmaltsp
chmaltsp force-pushed the fix/update-wizard-0.42.0 branch from 6984fef to 975902a Compare August 27, 2026 23:56
@razor-x razor-x changed the title fix: Update wizard to 0.42.0 feat: Update wizard to 0.42.0 Aug 28, 2026
@razor-x
razor-x merged commit 8ca4a82 into main Aug 28, 2026
14 checks passed
@razor-x
razor-x deleted the fix/update-wizard-0.42.0 branch August 28, 2026 04:04
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.

2 participants