feat: upgrade standardserver to 0.4.2 - #1667
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
More templates
@orpc/arktype
@orpc/bun
@orpc/client
@orpc/cloudflare
@orpc/contract
@orpc/experimental-effect
@orpc/evlog
@orpc/json-schema
@orpc/nest
@orpc/next
@orpc/openapi
@orpc/opentelemetry
@orpc/pino
@orpc/publisher
@orpc/ratelimit
@orpc/server
@orpc/shared
@orpc/tanstack-query
@orpc/valibot
@orpc/zod
commit: |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — bumps @standardserver/* from 0.2.1 to 0.4.2 across the monorepo, refreshes the lockfile and workspace minimum-release-age exclusions, and adjusts the two RPC-link test expectations for the new peer request encoding shape.
- Bumps
@standardserver/core,@standardserver/fetch,@standardserver/node,@standardserver/peer, and@standardserver/shareddependency ranges to^0.4.2in the root and every affected package. - Updates
pnpm-workspace.yamlminimumReleaseAgeExcludeentries to0.4.2. - Removes the
bodyHint: 'json'assertion frompackages/client/src/adapters/message-port/rpc-link.test.tsandpackages/client/src/adapters/websocket/rpc-link.test.tsto match standardserver 0.4.2's request peer message format. - Regenerates
pnpm-lock.yaml; besides the explicit standardserver bump it also pulled in incidental semver-compatible updates (e.g.crossws@0.4.10,eslint@10.7.0).
I verified the change by refreshing node_modules (corepack pnpm install --ignore-scripts), then running the affected adapter tests and the broader packages/client, packages/server, and tests/rpc suites — all passed.
Kimi K2 (free via Pullfrog for OSS) | 𝕏
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |

No description provided.