yrby-actioncable 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c0c73db294d14b5f9f9a4caecd1ef6d6e5f90fbed04f56485f0a30f0273f9a2c
-  data.tar.gz: b600ef54c94358690e42eadbb1e18c7bb49f847779fdb6bdb82829454f80fc6d
+  metadata.gz: 1ab50fed7379fc20924fec613bc32b7c4b34f2cac85ed446c6f562bd31ae3f5f
+  data.tar.gz: 7d17034c1eca75b303c4c0b839f7b14c1c23745ce3629b8e68cb21e161570bef
 SHA512:
-  metadata.gz: 97cdf721058d71485a590e0fb0b64fd5d1c05ba21df712d6ce0594ddb6a1f78c1cf2cf6492351092bfbd53412279e352311633367907adcbcdd33c3ef7934754
-  data.tar.gz: c3f0b6505bdb923ea48a0909e65d4ce3d9a68e933e3ba8bead8415facba3a8203ca3201e44e8bef18f732781968d917fde1972ab534abdcf68777c9fe97d8dd1
+  metadata.gz: '06697a55539569ee6010e11d6b80c5eaceb6e9643c71f355c91a4e286aaf664a00698ef1893cc37dd5005e6d47fcfcac6a08b352029f3866da2660d918269995'
+  data.tar.gz: 7a3cab1a4fe6d5171ac7ada2312cc6ece5dbd10e896c27132927d158ce19dae1e6ac06b768ad392b20ba8def7c0579eaa314f67d01f0c3dbf07ac74b92aaec9a

data/CHANGELOG-actioncable.md

@@ -6,6 +6,13 @@ this project aims to follow [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.1] - 2026-06-29
+
+### Changed
+- **Internal:** ActionCable stream-name prefix `y_ruby:` → `yrby:`.
+  Server-internal (broadcast + `stream_from` both use it) — no public API or
+  client-facing wire change. Depends on `yrby >= 0.2.1`.
+
 ## [0.2.0] - 2026-06-28
 
 First release under the **`yrby-actioncable`** name (previously developed as
@@ -14,8 +21,9 @@ First release under the **`yrby-actioncable`** name (previously developed as
 ### 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"`. ActionCable
-  stream prefix `yrb_lite:` → `y_ruby:`. Depends on `yrby >= 0.2.0`.
+  `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`.
 
 ### Notes
 - Full y-websocket protocol over ActionCable/AnyCable: origin-filtered relay,

data/README.md

@@ -20,7 +20,7 @@ end
 ```
 
 On the browser, use the `ActionCableProvider` from the 
-[`@yrby/client`](https://www.npmjs.com/package/@yrby/client) npm package.
+[`yrby-client`](https://www.npmjs.com/package/yrby-client) npm package.
 Integrates with any editor that includes Y.js support, such as Tiptap, ProseMirror
 and [Lexxy](https://www.npmjs.com/package/lexxy-realtime).
 
@@ -30,7 +30,7 @@ Install the gem and npm package:
 
 ```
 gem install yrby-actioncable # depends on yrby
-npm install @yrby/client
+npm install yrby-client
 ```
 
 ## What you get
@@ -59,7 +59,7 @@ guarantees, correctness, and thread safety.
 
 Towards that goal, `yrby` adds capabilities that may even stand out in the Yjs ecosystem:
 
-- Built-in update acknowledgement: the `ActionCableProvider` in `@yrby/client` will continue to
+- 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)
   only sends an ack when applying an update is successful. The goal is at-least-once delivery,
   and because CRDTs are idempotent a duplicate update is effectively a no-op.
@@ -197,7 +197,7 @@ for the same document as long as they share the same store and cable adapter.
 
 `on_load` and `on_change` are required. If either is missing, the channel fails 
 before it can acknowledge or broadcast edits. Presence is ephemeral:
-awareness frames are relayed, and `@yrby/client` sends a best-effort
+awareness frames are relayed, and `yrby-client` sends a best-effort
 presence-removal frame on disconnect/pagehide, with the client-side awareness
 timeout as the fallback for abrupt disconnects.
 
@@ -315,7 +315,7 @@ client -> server   { "update": "<base64 update>", "id": 42 }
 server -> client   { "ack": 42 }     # update accepted; safe to forget
 ```
 
-`@yrby/client`'s `ActionCableProvider` handles this automatically. It keeps
+`yrby-client`'s `ActionCableProvider` handles this automatically. It keeps
 the unacknowledged local document tail in a queue and sends the merged tail as a
 single causally-complete delta. The id is the highest sequence in the batch, so
 one `{ ack: id }` cumulatively confirms everything up to it. Because CRDT apply
@@ -324,7 +324,7 @@ re-acks. Awareness stays ephemeral and is not acked.
 
 Presence (cursors, selections) is owned by the browser clients — the server
 never sets or holds presence state, it only relays awareness frames opaquely.
-See `@yrby/client` for the client-side awareness API.
+See `yrby-client` for the client-side awareness API.
 
 ## Thread Safety
 

data/lib/y/action_cable/sync.rb

@@ -296,7 +296,7 @@ module Y::ActionCable # rubocop:disable Style/ClassAndModuleChildren
     end
 
     def sync_stream_name
-      "y_ruby:#{@sync_key}"
+      "yrby:#{@sync_key}"
     end
 
     def sync_awareness_stream_name

data/lib/y/action_cable/version.rb

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

metadata

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