refactor(publisher,bun,cloudflare)!: rename replay option to resume#1711
Merged
dinwwwh merged 1 commit intoJul 23, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
More templates
@orpc/ai-sdk
@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/pinia-colada
@orpc/pino
@orpc/publisher
@orpc/ratelimit
@orpc/server
@orpc/shared
@orpc/tanstack-query
@orpc/trpc
@orpc/valibot
@orpc/zod
commit: |
Contributor
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — This mechanical breaking change renames the event-resumption replay option to resume across all publisher adapters (MemoryPublisher, RedisPublisher, UpstashPublisher, BunRedisPublisher) and the Cloudflare DurablePublisherObject, plus their tests, docs, and playgrounds.
- Renamed public option — Every adapter now accepts
resume: { enabled, seconds }instead ofreplay. - Renamed Cloudflare types and storage class —
DurablePublisherObjectReplayOptionsis nowDurablePublisherObjectResumeOptions; the internal storage class is now namedResumeStorage. - Updated test fixtures and bindings — Cloudflare worker test durable-object names and wrangler bindings moved from
PublisherReplay3sDO/PUBLISHER_REPLAY3S_DONtoPublisherResume3sDO/PUBLISHER_RESUME3S_DON. - Docs and playgrounds updated — All VitePress publisher examples and every playground context file use the new
resumeoption.
Kimi K2 (free via Pullfrog for OSS) | 𝕏
Contributor
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
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.
Renames the event
replayfeature toresumeacross all publisher adapters. The feature lets subscribers continue fromlastEventIdafter a disconnect —resumematches that purpose (and the v1 naming), whilereplaysuggested full event-history replay.replayoption →resumeinMemoryPublisher,RedisPublisher,UpstashPublisher,BunRedisPublisher, andDurablePublisherObjectDurablePublisherObjectReplayOptionstype →DurablePublisherObjectResumeOptions