Repository navigation
chore: bump tsx dev dependency to 4.23.0 - #12
Merged
Merged
Conversation
Refresh the tsx dev dependency from 4.22.4 to 4.23.0 (within the existing ^4.19.0 range — lockfile-only, no manifest range change). Low-risk minor bump picked up during a package-freshness audit while parking the repo. Deliberately held back (not staleness — decisions for when active work resumes): @types/node stays on 22.x to track the Node >=20 engines floor; typescript 5.9 (TS 7 is the native rewrite, a real migration); zod 3 (the @modelcontextprotocol/sdk peer is still on zod 3). Build + full test suite green; pnpm audit clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Refresh the
tsxdev dependency from 4.22.4 → 4.23.0. Within the existing^4.19.0range, so this is a lockfile-only change — no manifest range bump. Picked up during a package-freshness audit while parking the repo.Deliberately held back
Not staleness — each is a decision to make when active work resumes:
@types/nodestays on 22.x to track the Node ≥20 engines floor (bumping to 26's types would surface APIs the min-supported Node lacks).typescriptstays on 5.9 — TS 7 is the native (Go) rewrite, a real migration.zodstays on 3 — the@modelcontextprotocol/sdkpeer is still on zod 3.Verification
pnpm -r build✅pnpm -r test✅ (qrc transport, cli, mcp-over-mock 25 tools, auto-reconnect)pnpm audit --prod✅ no known vulnerabilities🤖 Generated with Claude Code