yrby-actioncable 0.2.1 → 0.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1ab50fed7379fc20924fec613bc32b7c4b34f2cac85ed446c6f562bd31ae3f5f
-  data.tar.gz: 7d17034c1eca75b303c4c0b839f7b14c1c23745ce3629b8e68cb21e161570bef
+  metadata.gz: 761e38cb9b0e73b19aef2bc906d4170bc340c54fe09cae9aa6099814a7876dbb
+  data.tar.gz: 83d55bc7f20aca3cf82e7ee46adf6c8a163638f468afb1de35b339b5167a913e
 SHA512:
-  metadata.gz: '06697a55539569ee6010e11d6b80c5eaceb6e9643c71f355c91a4e286aaf664a00698ef1893cc37dd5005e6d47fcfcac6a08b352029f3866da2660d918269995'
-  data.tar.gz: 7a3cab1a4fe6d5171ac7ada2312cc6ece5dbd10e896c27132927d158ce19dae1e6ac06b768ad392b20ba8def7c0579eaa314f67d01f0c3dbf07ac74b92aaec9a
+  metadata.gz: 07d8e355e0eb3fa8fba54bb33a9250a7e5cc932e5a0dc0ab042b4aad96f07df010b2601f8b3f20f26733f5112639ee38b0b15fc089846e8b379862c4193ef156
+  data.tar.gz: 94d632ddca4cdebab57f63eb75d82bf94264bf1a2031baf5a50151d3564b10b4b6f904815cc95fd9b7726eddfb1fad7eb7d77454b916d5d54a6089afeac50527

data/CHANGELOG-actioncable.md

@@ -6,6 +6,18 @@ this project aims to follow [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.2] - 2026-07-01
+
+### Changed
+- Raised the `yrby` floor to `>= 0.2.3`. That release makes `Doc#update_advances?`
+  exact for **delete-bearing** updates. The sync channel gates durable
+  record-before-distribute on `update_advances?` (`return :applied unless
+  doc.update_advances?(update)`), so with an older core a lost-ack retry of a
+  deletion the server had already integrated was re-recorded and re-broadcast
+  each time. No code change here — pinning the floor just makes the gem's
+  exactly-once durable-recording guarantee self-enforcing instead of dependent on
+  the app updating the core gem.
+
 ## [0.2.1] - 2026-06-29
 
 ### Changed
@@ -15,15 +27,8 @@ this project aims to follow [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [0.2.0] - 2026-06-28
 
-First release under the **`yrby-actioncable`** name (previously developed as
-`yrb-lite-actioncable`).
-
-### Changed
-- **Renamed `yrb-lite-actioncable` → `yrby-actioncable`.** Channel concern
-  `YrbLite::ActionCable::Sync` → **`Y::ActionCable::Sync`**; require
-  `require "yrb_lite/action_cable"` → `require "y/action_cable"`. (The stream
-  prefix shipped as `y_ruby:` in 0.2.0; see 0.2.1 for its rename to `yrby:`.)
-  Depends on `yrby >= 0.2.0`.
+First release. The y-websocket sync channel concern is **`Y::ActionCable::Sync`**,
+loaded with `require "y/action_cable"`. Depends on `yrby >= 0.2.0`.
 
 ### Notes
 - Full y-websocket protocol over ActionCable/AnyCable: origin-filtered relay,

data/README.md

@@ -41,23 +41,25 @@ npm install yrby-client
   one-include ActionCable concern.
 - Authoritative record-before-distribute semantics: each document change can be
   recorded durably before it goes out to anyone.
-- 
+- Optional server-side reads: `Doc#read_text` and `Doc#read_map` reconstruct a
+  document's contents in Ruby - no Node process - for search, exports, validation,
+  or server-side rendering.
 
-## Why "lite"
+## Scope
 
-The "lite" is the size of the surface. `yrby` binds just the part of `y-crdt` you
-need to *sync and persist* collaborative documents - a `Doc`, awareness, and the
-y-websocket protocol primitives. The Ruby side treats a document as opaque CRDT
-state: it applies updates, answers sync handshakes, and records deltas, but never
-reaches in to read or edit the contents. The browser editor owns the document's
-shape.
+`yrby` binds just the part of `y-crdt` you need to *sync and persist* collaborative
+documents - a `Doc`, awareness, and the y-websocket protocol primitives. By default
+the Ruby side treats a document as opaque CRDT state: it applies updates, answers
+sync handshakes, and records deltas without reaching into the contents - the browser
+editor owns the document's shape. When you do need to look inside, `Doc#read_text`
+and `Doc#read_map` reconstruct it server-side, in Ruby.
 
-## What isn't "lite"
+## Durability and delivery
 
-The surface area may be "lite", but a core focus is on durability, resiliency, delivery
+The surface is intentionally small, but the focus is durability, resiliency, delivery
 guarantees, correctness, and thread safety.
 
-Towards that goal, `yrby` adds capabilities that may even stand out in the Yjs ecosystem:
+Towards that goal, `yrby` adds capabilities that stand out even in the Yjs ecosystem:
 
 - Built-in update acknowledgement: the `ActionCableProvider` in `yrby-client` will continue to
   send updates until an ack is received from the server. [`yrby-actioncable`](https://rubygems.org/gems/yrby-actioncable)

data/lib/y/action_cable/version.rb

@@ -2,6 +2,6 @@
 
 module Y
   module ActionCable
-    VERSION = "0.2.1"
+    VERSION = "0.2.2"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: yrby-actioncable
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.2.2
 platform: ruby
 authors:
 - JP Camara
@@ -29,14 +29,14 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 0.2.1
+        version: 0.2.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 0.2.1
+        version: 0.2.3
 - !ruby/object:Gem::Dependency
   name: actioncable
   requirement: !ruby/object:Gem::Requirement