cross-tab-worker-databus 0.11.0 → 0.20.6

package/CHANGELOG.md

@@ -2,6 +2,215 @@
 
 本项目遵循 [Semantic Versioning](https://semver.org/)；变更记录格式参考 [Keep a Changelog](https://keepachangelog.com/)。
 
+## [0.20.6] - 2026-09-02
+
+### Added
+
+- Added a release checklist covering local gates, packed-consumer verification, tag creation, and manual npm publication.
+- Added migration guidance for pre-0.20 consumers and clarified that historical npm versions are immutable and are not republished from the current tree.
+
+## [0.20.5] - 2026-09-02
+
+### Added
+
+- Added public-consumer freeze coverage for root, hooks, Vue, and Centrifuge subpaths across ESM and CommonJS artifacts.
+- Declaration checks now verify the shipped `.d.ts` files and key replay, deduplication, and publication metadata types.
+
+## [0.20.4] - 2026-09-02
+
+### Added
+
+- Added a real Chromium multi-tab soak scenario covering repeated fan-out, owner migration, BFCache round trips, reload recovery, and duplicate-free delivery.
+- Browser regression coverage now exercises lifecycle transitions as one continuous session instead of isolated one-shot checks.
+
+## [0.20.3] - 2026-09-02
+
+### Added
+
+- Added React lifecycle coverage for dynamic topic changes.
+- Topic replacement now verifies old subscriptions are removed before the new topic is delivered, including end-to-end WebSocket hook wiring.
+
+## [0.20.2] - 2026-09-02
+
+### Added
+
+- Added protocol recovery coverage proving valid WebSocket publications continue after malformed binary and text frames.
+- Binary truncation, JSON parse failures, nested envelopes, and error isolation are now exercised as one compatibility sequence.
+
+## [0.20.1] - 2026-09-02
+
+### Added
+
+- Added persistence mutation-sequence soak coverage spanning hydration, retry recovery, topic cleanup, subsequent append, and full cleanup.
+- Recovery tests now verify that serialized persistence operations remain usable after transient failures.
+
+## [0.20.0] - 2026-09-02
+
+### Added
+
+- Formalized publication-envelope compatibility coverage across legacy, nested, fallback-topic, primitive payload, metadata, and unknown-field frames.
+- Empty or missing topics are rejected consistently while transport-supplied fallback channels remain supported.
+
+## [0.19.9] - 2026-09-02
+
+### Added
+
+- Added regression coverage for deduplication and replay/persistence composition.
+- Duplicate publications are verified not to pollute replay history, while IDs can re-enter history after TTL expiry.
+
+## [0.19.8] - 2026-09-02
+
+### Fixed
+
+- IndexedDB replay persistence now invalidates cached connections after transaction creation or request failures.
+- Closed or otherwise unusable connections can recover through the existing persistence retry path without recreating the adapter.
+
+## [0.19.7] - 2026-09-02
+
+### Fixed
+
+- IndexedDB replay persistence no longer permanently caches a rejected `open()` promise after transient initialization failures.
+- Subsequent persistence operations can reopen the database and recover without recreating the adapter.
+
+## [0.19.6] - 2026-09-02
+
+### Fixed
+
+- IndexedDB replay persistence now handles cross-tab `versionchange` events by closing stale connections and reopening on the next operation.
+- Multi-tab schema changes no longer leave the adapter permanently bound to an invalid connection.
+
+## [0.19.5] - 2026-09-02
+
+### Fixed
+
+- React `useCrossTabDataBus` now ignores stale effect generations during rapid dependency changes.
+- Superseded asynchronous cleanup can no longer clear or overwrite the newest bus lifecycle.
+
+## [0.19.4] - 2026-09-02
+
+### Fixed
+
+- Vue `useCrossTabDataBus` now guards against stale asynchronous stop/start completions during rapid reactive dependency changes.
+- A superseded lifecycle no longer resurrects an obsolete bus instance after a newer dependency update.
+
+## [0.19.3] - 2026-09-02
+
+### Added
+
+- Added optional `dedup.sweepMs` for periodic expiry cleanup during quiet periods.
+- Dedup sweep timers follow start/resume and pagehide/stop lifecycle boundaries.
+
+## [0.19.2] - 2026-09-02
+
+### Fixed
+
+- Pending persistence retries are cancelled across `stop()` and pagehide suspension boundaries.
+- Lifecycle-cancelled retries no longer emit persistence errors or start another adapter attempt.
+
+## [0.19.1] - 2026-09-01
+
+### Fixed
+
+- WebSocket transport now accepts browser `Blob` binary frames and decodes them through the existing ArrayBuffer protocol path.
+- Blob conversion failures are isolated through the transport error handler without crashing the message callback.
+
+## [0.19.0] - 2026-09-01
+
+### Added
+
+- Persistence retry now emits opt-in `reliability` trace events with the bounded operation name and retry attempt.
+- Retry diagnostics cover `load`, `append`, `clear`, `clearTopic`, and `clearBefore` without exposing payloads or error bodies.
+
+### Compatibility
+
+- Tracing remains disabled by default; retry timing, adapter contracts, and final error behavior are unchanged.
+
+## [0.18.0] - 2026-09-01
+
+### Added
+
+- Added opt-in `replay.persistenceRetry` with bounded attempts and exponential backoff for transient persistence failures.
+- Replay append, hydrate, clear, topic cleanup, and retention cleanup now share the same retry policy.
+- Exported `DataBusPersistenceRetryOptions` for typed configuration.
+
+### Compatibility
+
+- The default retry policy is one attempt, preserving existing persistence behavior and error timing.
+- Persistence adapters remain unchanged; retry orchestration stays in `CrossTabDataBus`.
+
+## [0.17.0] - 2026-09-01
+
+### Added
+
+- Added optional `replay.retentionSweepMs` for periodic durable replay retention cleanup when no new publications arrive.
+- Retention sweeps follow the DataBus lifecycle: start/resume enables the timer, while pagehide/stop disables it.
+- Added fake-clock lifecycle coverage for timer cleanup and invalid sweep intervals.
+
+### Compatibility
+
+- `retentionSweepMs` is opt-in and has no effect without both `retentionMs` and a persistence adapter implementing `clearBefore()`.
+- Existing publication-triggered cleanup, manual cleanup, and replay persistence contracts remain unchanged.
+
+## [0.16.0] - 2026-09-01
+
+### Added
+
+- Replay retention cleanup is coalesced during publication bursts; the newest cutoff wins while cleanup mutations remain serialized.
+- WebSocket binary-frame compatibility coverage now verifies truncated, invalid-magic, and incomplete-header frames are ignored safely.
+
+### Compatibility
+
+- Retention cleanup remains opt-in through `replay.retentionMs`; manual `clearReplayBefore()` behavior is unchanged.
+- Existing JSON, nested publication-envelope, and legacy binary payload formats remain supported.
+
+## [0.15.0] - 2026-09-01
+
+### Fixed
+
+- Replay retention now preserves legacy messages that do not carry an explicit producer timestamp; only timestamped messages older than the cutoff are removed.
+
+### Added
+
+- Trace event timestamps accept an injectable `trace.now` clock for deterministic lifecycle and metrics tests.
+- Added compatibility coverage for timestamp-less replay cleanup and injected trace clocks.
+
+### Compatibility
+
+- Existing `DataBusTraceOptions` and replay persistence adapters remain source-compatible; wall-clock behavior remains the default.
+
+## [0.14.0] - 2026-09-01
+
+### Fixed
+
+- Vue `useCrossTabSubscription` now rebinds when a reactive topic changes on the same bus instance.
+
+### Added
+
+- Vue topic-switch lifecycle regression coverage.
+- Release scope documents cross-page replay mutation ordering and adapter parity guarantees.
+
+## [0.13.0] - 2026-09-01
+
+### Added
+
+- IndexedDB replay mutations are serialized per adapter instance, preventing concurrent append read-modify-write races from losing history.
+- Dedup memory is reset as part of a full stop lifecycle, so a restarted bus begins with a clean delivery window.
+- Added persistence-failure diagnostics and lifecycle regression coverage.
+
+## [0.12.0] - 2026-09-01
+
+### Added
+
+- Deduplication TTL now accepts an injectable `dedup.now` clock for deterministic tests and host runtimes without a wall-clock dependency.
+- Persistence failures in replay append/cleanup paths emit bounded `persistence_cleanup` reliability diagnostics before reaching error handlers.
+- Publication parsing now accepts only non-empty message IDs and finite timestamps, while preserving legacy payload compatibility.
+- Added protocol compatibility tests for legacy, nested, fallback-topic, and malformed metadata frames.
+
+### Compatibility
+
+- `dedup.now` is optional and existing configurations keep wall-clock behavior.
+- Invalid metadata is ignored instead of poisoning a publication; the topic and payload remain deliverable.
+
 ## [0.11.0] - 2026-09-01
 
 ### Added

package/dist/centrifuge.js

@@ -2,7 +2,7 @@ import {
   CrossTabDataBus,
   parseDataBusPublication,
   selectWorkerBackend
-} from "./chunk-NX76TAV3.js";
+} from "./chunk-LPS4XOK4.js";
 
 // src/centrifuge-session.ts
 import { Centrifuge } from "centrifuge";

package/dist/centrifuge.shared.worker.js

@@ -4993,11 +4993,13 @@ function parseDataBusPublication(value, fallbackTopic) {
   if (!topic) return null;
   const hasMetadataEnvelope = fallbackTopic !== void 0 && Object.prototype.hasOwnProperty.call(publication, "data") && (typeof publication.messageId === "string" || typeof publication.timestamp === "number");
   const data = nested || fallbackTopic === void 0 || hasMetadataEnvelope ? publication.data : value;
+  const messageId = typeof publication.messageId === "string" && publication.messageId.length > 0 ? publication.messageId : void 0;
+  const timestamp = typeof publication.timestamp === "number" && Number.isFinite(publication.timestamp) ? publication.timestamp : void 0;
   return {
     topic,
     data,
-    ...typeof publication.messageId === "string" ? { messageId: publication.messageId } : {},
-    ...typeof publication.timestamp === "number" ? { timestamp: publication.timestamp } : {}
+    ...messageId === void 0 ? {} : { messageId },
+    ...timestamp === void 0 ? {} : { timestamp }
   };
 }