Shipped · APIs and backends

What middleapi/orpc shipped

The public repository of Orpc · github.com/middleapi/orpc

Written by FoxPlug from the repository's own releases; not affiliated with Orpc. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/middleapi/orpc; Orpc did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for orpc, free

Week of November 2, 2026

What shipped

Why it matters

This week is largely about correctness at the edges: RPC and batch clients now fail loudly on malformed or redirected responses instead of resolving something misleading, and several stream and dedupe paths stop leaking listeners, streams or stale writes. OpenAPI generation got closer to the runtime behavior by serializing before downgrade, sanitizing component names and fixing discriminator refs, while two breaking fixes narrow option types before v2 stable.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: RPCLink rejects 3xx responses, malformed RPC success bodies now throw MalformedResponseError, abort listeners are cleaned up after deduped calls settle, and OpenAPI component names are sanitized to valid keys.

Post for LinkedIn

This week in oRPC: RPCLink now throws on 3xx responses instead of resolving a redirect body as output, and malformed 2xx JSON bodies are rejected with MalformedResponseError. Dedupe no longer keeps abort listeners after a request settles, batch streaming cancels the response stream on decode errors, and data-less SSE error events are preserved. On the OpenAPI side, documents are serialized before downgrading to 3.1 or 3.0, component names are sanitized to valid keys, and discriminator mapping refs are rewritten when $defs are hoisted. Also: the RPC outputStatus option must now resolve to a number.

Week of October 26, 2026

What shipped

Why it matters

This week shipped a beta with new client and server plugins, including a cookie jar for non-browser clients and HEAD support for GET procedures, plus a streaming option for batch responses. It also brought breaking changes to OpenAPI error response options and several fixes to OpenAPI generation and RPC deserialization that affect people upgrading.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V2.0.0-beta.48 is out: a cookie jar for clients outside the browser, HEAD support for GET procedures, a streaming option for batch responses, and a new OpenAPI router. Error response body options no longer fall back to defaults.

Post for LinkedIn

V2.0.0-beta.48 is out. It adds CookieJarLinkPlugin and CookieJar for clients outside the browser, HeadMethodHandlerPlugin for HEAD requests against GET procedures, a streaming mode for BatchLinkPlugin, and a new OpenAPI router. One breaking change: error response body options no longer fall back to the default behavior, so each option now always decides. This week also fixed RPC deserialization of unknown meta types and made wrapped readable streams read on demand.

Week of October 19, 2026

What shipped

Why it matters

This week brings a large v2 beta with breaking changes and moves the Effect and MSW integrations out of experimental naming. It also adds type-aware keys and structural sharing across the query adapters and a prefix method on adapters, which change how inputs hash and how scoping works. Several fixes address retries, iterator cancellation and serialization so remote and streaming calls behave more predictably.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V2.0.0-beta.46 is out: only jsonified client factories in createContractJsonifiedUtilsFactory, internal-only exports removed. Adapters gained a prefix() method, TanStack Query and Pinia Colada keys are now type-aware, and @orpc/effect plus @orpc/msw drop the experimental prefix.

Post for LinkedIn

This week's releases include v2.0.0-beta.46, which makes breaking changes: createContractJsonifiedUtilsFactory now accepts only jsonified client factories and internal-only APIs are no longer exported. Publisher, rate limiter and lock adapters gained a prefix() method that returns a scoped adapter sharing the original client. TanStack Query now uses type-aware structural sharing and serialized input keys, and Pinia Colada gained a configurable key serializer. The Effect integration is now published as @orpc/effect and the MSW integration as @orpc/msw, both dropping the experimental prefix. Fixes cover iterator retries after close, durable iterator token refresh failures, and primitive conversion for router utils and error constructor maps.

Week of October 12, 2026

What shipped

Why it matters

This week is mostly security hardening: several fixes close unauthenticated CPU and memory exhaustion paths in the RPC serializer, matcher, file uploads and event replay, plus a URL construction issue in OpenAPILink. There is also a breaking change in how client links report malformed responses. Users on affected versions should upgrade, and those relying on MALFORMED_ORPC_RESPONSE error handling should adjust their code.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V2.0.0-beta.44 is out. Malformed responses now throw MalformedResponseError directly, and buffered batches switch to streaming when a sub-response is a stream. This week also shipped hardening: bigint digit caps, meta path checks in RPC deserialize, canonical base64url in unsign/

Post for LinkedIn

This week brought v2.0.0-beta.44 and v1.15.7, along with a set of security hardening fixes. Client links now throw MalformedResponseError directly instead of wrapping it in an ORPCError, and buffered batches switch to streaming when a sub-response is a stream. On the hardening side: bigint digit counts are capped in the RPC serializer and smart coercion, meta paths that descend into already deserialized values are rejected, unsign and decrypt reject non-canonical base64url, the lazy router prefix scan is bounded, small uploads stay in memory, and OpenAPILink encodes a leading slash in first-segment catch-all params. If you use RPC or OpenAPI links, review the breaking change before upgrading.

Week of October 5, 2026

What shipped

Why it matters

This week's work tightens the OpenAPI surface: memory use for bracket notation keys is bounded, enum and union statuses are supported in detailed responses, and path params win over colliding body or query keys in compact input. Several fixes prevent silent data problems, from Cloudflare message ids skipping events after a table recreation to retries of request bodies that cannot be resent. Peer dependency floors were raised so mutation interceptors behave correctly on supported TanStack Query and Pinia Colada versions.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

New release: OpenAPI detailed responses now support enum and union statuses, bracket notation keys use bounded memory, and path params take precedence in compact input. Also: timestamp-based Cloudflare message ids, no retry of non-resendable bodies, and higher TanStack Query and

Post for LinkedIn

This week we shipped changes across the OpenAPI layer and a few important fixes. OpenAPI detailed responses now accept enum and union status codes, including picklists from Effect, arktype and valibot. Bracket notation deserialization tracks empty slots across the payload to bound memory while allowing longer sequential arrays, and path params now take precedence over colliding query or body keys in compact input. On the fixes side, Cloudflare message ids are timestamp based so resuming after idle cleanup or a schema reset does not skip newer events, the Retry After Link Plugin skips requests whose bodies cannot be resent, and path matching handles raw and percent-encoded characters. We also raised the TanStack Query and Pinia Colada peer dependency floors because older TanStack versions p

Week of September 28, 2026

What shipped

Why it matters

This week focused on robustness in streaming and batch operations, fixing edge cases where cancelled requests continued running and async context was lost between callers. The JSON Schema and OpenAPI improvements ensure types round-trip correctly and special values like Infinity serialize properly. These fixes matter because they prevent silent failures in production where batched calls, streams, and context-aware transports are heavily used.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V2.0.0-beta.42: batch streams now cancel properly, async context flows correctly between callers, Infinity round-trips through serializers, and JSON Schema handles dates and composed types.

Post for LinkedIn

V2.0.0-beta.42 ships fixes for batch and streaming reliability. Cancelled streams now properly stop on the server instead of running indefinitely, batched requests preserve caller async context so request-scoped data stays intact, and infinity values round-trip through serializers. We also improved JSON Schema handling for dates, tuples, and composed types, and OpenAPI path matching now correctly handles catch-all parameters and special characters.

Week of September 21, 2026

What shipped

Why it matters

This week addresses critical reliability issues in streaming, batching, and event delivery, plus mass-assignment and security gaps. Connection lifecycle handling across multiple transports is now correct, and procedures respect schema boundaries properly. These fixes prevent data loss, resource leaks, and vulnerability exposure.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: Redis events now stay in order, batches and subscriptions stop on disconnect, retry loops don't freeze, and procedures respect their schemas. 40 fixes across transport, validation, and streaming.

Post for LinkedIn

Orpc shipped 40 fixes this week focusing on reliability and correctness. Redis Pub/Sub now guarantees event ordering during resume, client disconnects properly cancel streamed responses and batched work, and procedures no longer receive undeclared fields. RetryLinkPlugin no longer hangs on errors, and batching gains a configurable wait option to optimize request grouping. These changes address streaming leaks, mass-assignment risks, and connection lifecycle issues across WebSocket, MessagePort, and HTTP transports.

Week of September 14, 2026

What shipped

Why it matters

Beta.37 hardens security with type checking during deserialization and removes deprecated adapter-level hooks, while beta.36 expanded platform support with distributed locks and NestJS QUERY method. These releases improve both safety and flexibility for developers building production systems.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V2.0.0-beta.37 and beta.36 shipped this week. Beta.37 removes adapter interceptors, hardens RPC deserialization against type confusion, and fixes plugin ordering. Beta.36 adds distributed locking, NestJS QUERY support, and Redis cluster adapters.

Post for LinkedIn

Two oRPC beta releases landed this week with significant improvements: v2.0.0-beta.37 removes deprecated adapter-level interceptors and plugins, hardens the RPC serializer to validate wire types before restoring built-in values, fixes plugin registration order, and lets handlers accept context functions resolved after prefix checks. v2.0.0-beta.36 introduces distributed locking helpers with multiple adapters, adds NestJS support for HTTP QUERY method on v11.2+, and extends rate limiting to accept Redis cluster clients. Documentation now clarifies that any Standard Schema library works with oRPC, not just the three highlighted packages.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-10.

Is this your repo? Ask us to remove this page.