Skip to content

Bump dependencies to latest and upload-artifact to v7 - #56

Open
DennisAlund wants to merge 4 commits into
mainfrom
claude/ecstatic-pasteur-iz7o9i
Open

Bump dependencies to latest and upload-artifact to v7#56
DennisAlund wants to merge 4 commits into
mainfrom
claude/ecstatic-pasteur-iz7o9i

Conversation

@DennisAlund

Copy link
Copy Markdown
Member

Summary

Routine dependency maintenance: bump manifests toward their latest published versions and bring GitHub Actions up to date.

  • Root package.json: bumped devDependencies (@cloudflare/vitest-pool-workers, tsx, vitest + plugins, wrangler, @cloudflare/workers-types) and dependencies (@cloudflare/workers-oauth-provider, @hono/zod-openapi, hono, jose, zod) to latest.
  • sdk/typescript/package.json: bumped vitest to latest.
  • sdk/python/pyproject.toml: raised mypy/ruff dev floors to latest (httpx, pytest, pytest-asyncio, respx were already current).
  • sdk/dart/pubspec.yaml: no change — all four dependencies (http, meta, lints, test) were already at their latest pub.dev versions.
  • .github/workflows/ci.yml: actions/upload-artifact bumped v4v7. Every other action across .github/workflows/* was already pinned to its current latest major (actions/checkout@v7, actions/setup-node@v7, actions/setup-python@v7, dart-lang/setup-dart@v1, pypa/gh-action-pypi-publish@release/v1).

Deliberately not bumped

Two dependencies would break the build if moved to their published "latest", so they're pinned where they were:

  • typescript (root and TypeScript SDK) stays ^6.0.3. TypeScript 7 tightens overload resolution for handlers that return Promise<Response> | JSONRespondReturn<...>, breaking tsc --noEmit across roughly a dozen Hono routes in src/index.tsx. It also crashes tsup's dts bundling step in the SDK build (rollup-plugin-dts reads an API TS 7 no longer exposes the same way). Both are source-level migrations, not version bumps, so out of scope here.
  • agents stays ^0.19.0, and @modelcontextprotocol/sdk stays at 1.29.0. agents@0.22.0 requires the new @modelcontextprotocol/client/@modelcontextprotocol/server 2.0.0 packages, which replace @modelcontextprotocol/sdk in a breaking split — an MCP transport migration, not a dependency bump. agents@0.19.0 also pins an exact nested @modelcontextprotocol/sdk@1.29.0, so bumping the top-level package alone duplicates the SDK's classes across two module instances and breaks typecheck on ShrtnrMCP's server property.

No SDK surface changed, so no SDK version/CHANGELOG bumps and no spec-hash drift (./scripts/spec-hash.sh unchanged and matches all three recorded hashes).

Testing

  • yarn tsc --noEmit — pass
  • yarn test — 86 files / 1284 tests pass
  • yarn e2e — pre-existing failure in this sandbox unrelated to this change: Chromium logs net::ERR_CONNECTION_RESET / net::ERR_CERT_AUTHORITY_INVALID console errors that the smoke/links specs assert against. Reproduces identically on main with only the sandbox's browser-executable-path workaround applied (no dependency changes), so it's an environment/network constraint of this container, not a regression. Should be re-verified in CI.
  • sdk/typescript: yarn build and yarn test (79 tests) — pass
  • sdk/python: ruff check, ruff format --check, mypy --strict, pytest (97 tests) — pass
  • sdk/dart: not run (Dart SDK unavailable in this sandbox); no changes were made to sdk/dart/pubspec.yaml

🤖 Generated with Claude Code


Generated by Claude Code

claude added 4 commits August 28, 2026 19:26
Upgraded devDependencies (@cloudflare/vitest-pool-workers, tsx, vitest
and its plugins, wrangler, @cloudflare/workers-types) and dependencies
(@cloudflare/workers-oauth-provider, @hono/zod-openapi, hono, jose,
zod) to their latest published versions.

Kept typescript at ^6.0.3: TypeScript 7 tightens overload resolution
for handlers returning Promise<Response> | JSONRespondReturn<...> and
breaks typecheck across roughly a dozen Hono routes in src/index.tsx.
Fixing that is a source-level migration, not a dependency bump.

Kept agents at ^0.19.0 and @modelcontextprotocol/sdk at 1.29.0:
agents@0.22.0 requires the new @modelcontextprotocol/client and
@modelcontextprotocol/server 2.0.0 packages, which replace
@modelcontextprotocol/sdk in a breaking split; that's an MCP transport
migration, not a version bump. agents@0.19.0 also pins an exact nested
@modelcontextprotocol/sdk@1.29.0, so bumping the top-level package
alone duplicates the SDK's classes under two module instances and
breaks typecheck on ShrtnrMCP's server property.

yarn tsc --noEmit and yarn test (86 files, 1284 tests) pass.
Upgraded vitest to ^4.1.11. Kept typescript at ^6.0.3: TypeScript 7
crashes tsup's dts bundling step (rollup-plugin-dts reads an
undefined useCaseSensitiveFileNames off the TS 7 API), so yarn build
fails outright. No SDK surface change, no version or CHANGELOG bump.

yarn build and yarn test (79 tests) pass.
mypy>=2.3.1, ruff>=0.16.5. httpx, pytest, pytest-asyncio and respx
were already at their latest published versions. No SDK surface
change, no version or CHANGELOG bump.

ruff check, ruff format --check, mypy --strict and pytest (97 tests)
pass.
Every other action across .github/workflows/* (actions/checkout@v7,
actions/setup-node@v7, actions/setup-python@v7, dart-lang/setup-dart@v1,
pypa/gh-action-pypi-publish@release/v1) is already pinned to its latest
major. actions/upload-artifact was still on v4; the with: inputs (name,
path, retention-days) are unchanged across v4-v7, so this is a drop-in
bump.
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
shrtnr 1bc0873 Aug 28 2026, 07:28 PM

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