yrby 0.2.0-x86_64-linux → 0.2.1-x86_64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 190e8fcd0e546ba141c5d61ab0edc08322485c886b8df71d5e6318e12d43d0fe
-  data.tar.gz: 34257806d2f7d5f2a5f48a4f2f84c2357d1625dfa695edf20c3539c750397db0
+  metadata.gz: ff22dc8ae310daac142d0fe476d8659cfedff1b1f5cb88ccc9c46688e03fbe27
+  data.tar.gz: e3ff8171d93f3785b1d349173b7b7ebf12e1f762ea172bf48c4f9c7c40a0255f
 SHA512:
-  metadata.gz: 49c9699c255ffaa95f39609d1860d691f2b66915da8ba0b8556a327111f1f05b8dc980fd4eb5f9284f6ddc6bfb4256359d62491187efb2e6ac945ce5d6a678a2
-  data.tar.gz: 811c437653af02e71002324bc23f3e84390305ea8fb3f2e66dcdb4075afd21f451cebb915e7c97b1b99e5d0b95363474e0785602b50e8c94a6161611288a086a
+  metadata.gz: 4f3c2c3291521f47218ed70e4f2d9205efe7143312588d755079e87bbee32ac60e4c0fc45f7156453cc54c695d702ae53e91be8904cd6d1436551b8d10cddd31
+  data.tar.gz: 6796d3d50aceac6f5924be12d9cb9b1beb9ef8b3c80a75745d88f0b04dd930e1af9abb3119bd495b358af08a5703e58a45a368af9cea3c460b36bd45c9cc0054

data/CHANGELOG.md

@@ -6,6 +6,13 @@ to follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.2.1] - 2026-06-29
+
+### Changed
+- **Internal:** renamed the native extension crate `y_ruby` → `yrby` (now loads
+  from `lib/y/yrby.bundle`). No public API change — `require "y"` and `Y::Doc`
+  are unchanged.
+
 ## [0.2.0] - 2026-06-28
 
 First release under the **`yrby`** name (the project was previously developed
@@ -15,8 +22,8 @@ mirroring the `y-rb` gem's `Y::Doc` interface.
 ### Changed
 - **Renamed `yrb-lite` → `yrby`.** Module `YrbLite` → top-level `Y`
   (`Y::Doc`, `Y::Error`, `Y::VERSION`). Require path `require "yrb_lite"` →
-  `require "y"`. Native extension crate `yrb_lite` → `y_ruby`, loaded from
-  `lib/y/y_ruby.bundle`.
+  `require "y"`. (The native extension crate shipped as `y_ruby` in 0.2.0; see
+  0.2.1 for its rename to `yrby`.)
 
 ### Added
 - Native `Doc#read_text` and `Doc#read_map` readers — reconstruct plain text and

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/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Y
-  VERSION = "0.2.0"
+  VERSION = "0.2.1"
 end

data/lib/y.rb

@@ -3,13 +3,13 @@
 require_relative "y/version"
 
 # Load the native extension. Precompiled gems ship it in a per-Ruby-version
-# subdir (lib/y/<major.minor>/y_ruby.<ext>); a source build puts it flat at
-# lib/y/y_ruby.<ext>. Try the versioned path first, fall back.
+# subdir (lib/y/<major.minor>/yrby.<ext>); a source build puts it flat at
+# lib/y/yrby.<ext>. Try the versioned path first, fall back.
 begin
   RUBY_VERSION =~ /(\d+\.\d+)/
-  require_relative "y/#{Regexp.last_match(1)}/y_ruby"
+  require_relative "y/#{Regexp.last_match(1)}/yrby"
 rescue LoadError
-  require_relative "y/y_ruby"
+  require_relative "y/yrby"
 end
 
 module Y

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: yrby
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: x86_64-linux
 authors:
 - JP Camara
@@ -66,8 +66,8 @@ files:
 - LICENSE
 - README.md
 - lib/y.rb
-- lib/y/3.4/y_ruby.so
-- lib/y/4.0/y_ruby.so
+- lib/y/3.4/yrby.so
+- lib/y/4.0/yrby.so
 - lib/y/decoder.rb
 - lib/y/decoder/version.rb
 - lib/y/version.rb