fix: upgrade standard-server/* packages to 0.10.3

[dinwwwh]

Upgrades all @standard-server package dependencies across the monorepo from version 0.10.2 to 0.10.3.

Changes

• Updated @standard-server/* dependency versions in pnpm-workspace.yaml minimumReleaseAgeExclude list
• Updated @standard-server/* dependency versions in all package.json files:
  • packages/server: aws-lambda, core, fastify, fetch, node, peer
  • packages/client: core, fetch, peer
  • packages/node: core, fetch, node
  • packages/openapi: core, fetch, aws-lambda
  • packages/hibernation: core, peer
  • packages/nest: core, node
  • packages/bun: core
  • packages/cloudflare: core
  • packages/evlog: core
  • packages/pino: core
  • packages/publisher: core
  • packages/ratelimit: core
  • packages/shared: shared
  • Root package.json: core, fetch, peer, shared

All version constraints use the tilde range (~0.10.3) to allow patch-level updates.

https://claude.ai/code/session_0136VNEpZ9VctRgNrYHyJYfK

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

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

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	orpc	6ea50c5	Commit Preview URL Branch Preview URL	Oct 13 2026, 08:09 AM

[codspeed]

Merging this PR will degrade performance by 10.07%

⚠️ 5 benchmarks spent significant time in system calls

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

• range request
• serve file
• not modified (304)
• serve deeply nested encoded path
• not found fall through

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

❌ 1 regressed benchmark
✅ 27 untouched benchmarks
⏩ 2 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌ ⚠️	range request	1 ms	1.1 ms	-10.07%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing claude/beautiful-ride-hjqivc (6ea50c5) with main (0dd6994)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[pkg-pr-new]

More templates

• @orpc/bun-playground
• @orpc/cloudflare-playground
• @orpc/nest-playground
• @orpc/next-playground

@orpc/ai-sdk

npm i https://pkg.pr.new/@orpc/ai-sdk@2215

@orpc/arktype

npm i https://pkg.pr.new/@orpc/arktype@2215

@orpc/bun

npm i https://pkg.pr.new/@orpc/bun@2215

@orpc/client

npm i https://pkg.pr.new/@orpc/client@2215

@orpc/cloudflare

npm i https://pkg.pr.new/@orpc/cloudflare@2215

@orpc/contract

npm i https://pkg.pr.new/@orpc/contract@2215

@orpc/experimental-effect

npm i https://pkg.pr.new/@orpc/experimental-effect@2215

@orpc/evlog

npm i https://pkg.pr.new/@orpc/evlog@2215

@orpc/hibernation

npm i https://pkg.pr.new/@orpc/hibernation@2215

@orpc/json-schema

npm i https://pkg.pr.new/@orpc/json-schema@2215

@orpc/experimental-lock

npm i https://pkg.pr.new/@orpc/experimental-lock@2215

@orpc/experimental-msw

npm i https://pkg.pr.new/@orpc/experimental-msw@2215

@orpc/nest

npm i https://pkg.pr.new/@orpc/nest@2215

@orpc/next

npm i https://pkg.pr.new/@orpc/next@2215

@orpc/node

npm i https://pkg.pr.new/@orpc/node@2215

@orpc/openapi

npm i https://pkg.pr.new/@orpc/openapi@2215

@orpc/opentelemetry

npm i https://pkg.pr.new/@orpc/opentelemetry@2215

@orpc/pinia-colada

npm i https://pkg.pr.new/@orpc/pinia-colada@2215

@orpc/pino

npm i https://pkg.pr.new/@orpc/pino@2215

@orpc/publisher

npm i https://pkg.pr.new/@orpc/publisher@2215

@orpc/ratelimit

npm i https://pkg.pr.new/@orpc/ratelimit@2215

@orpc/server

npm i https://pkg.pr.new/@orpc/server@2215

@orpc/shared

npm i https://pkg.pr.new/@orpc/shared@2215

@orpc/swr

npm i https://pkg.pr.new/@orpc/swr@2215

@orpc/tanstack-query

npm i https://pkg.pr.new/@orpc/tanstack-query@2215

@orpc/trpc

npm i https://pkg.pr.new/@orpc/trpc@2215

@orpc/valibot

npm i https://pkg.pr.new/@orpc/valibot@2215

@orpc/zod

npm i https://pkg.pr.new/@orpc/zod@2215

commit: 6ea50c5

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[pullfrog]

✅ No new issues found.

Reviewed changes

Mechanical bump of all @standard-server/* deps from 0.10.2 → 0.10.3 across the monorepo; no src/ behavior change.

• 14 package.json ranges (~0.10.3) — root, bun, client, cloudflare, evlog, hibernation, nest, node, openapi, pino, publisher, ratelimit, server, shared.
• pnpm-lock.yaml — importer specifier/version, top-level packages: resolutions + integrity, and snapshots: all moved to 0.10.3 in lock-step.
• pnpm-workspace.yaml — minimumReleaseAgeExclude entries replaced (pruned, not appended) 0.10.2 → 0.10.3, matching the in-file "prune on each bump" comment.

Verification: grep for 0.10.2 across the repo returns zero remaining references; all 30 @standard-server/* declarations resolve to 0.10.3; and the lockfile integrity hashes for @standard-server/core@0.10.3 and @standard-server/shared@0.10.3 match the npm registry exactly. The lockfile also carries an incidental, harmless rettime 0.11.11 → 0.11.12 transitive refresh from regenerating the install — unrelated to this bump but benign.

  ^{｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}