vibe_zstd 1.3.0 → 1.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5eb8d0ac2293ee84d588b9eb237b0c3b4623989c4db8692ad1ab325fd8047695
-  data.tar.gz: 1732b409b13fd9e99fecb7ebf8d026f9b6d0119012641c96e66faa3d51c0f5ce
+  metadata.gz: f2a7e3f6643d3fd14ebce10d77ba79770d44c11cd82775de3cf2c24eaa84f118
+  data.tar.gz: de1a91cfa51e4e49e4759cf39449c309d28c985d2cf9085e1b6e8faed2b07e8c
 SHA512:
-  metadata.gz: 65cc971c6400d69adaca95b0c520c8bd8ec22648bdb57218f5ac833bd0a63db6908c953b4fca127753f2257f8502b34b89eb383c38a8f315431e4051ff7a9401
-  data.tar.gz: 836b8a52c28f8cd0d79ed4a8aa80a286f51dda58e1e483320f4544b2a63ded6e83cdccd3bfea122d267c9a44cb43dabbd2c12e69aeb69162d7d4f4ee7ecb60c3
+  metadata.gz: 8cb9a59f93e6167df9b7aa0a3ac466f37aae29aeb22aa191951714a694d6dc215f0f008e099f46f60c9e3941352d41c935e470e5301b9fa1cdefb980bf4372b8
+  data.tar.gz: 63bb4d19e418c713335da4ed48a05b11ff1af0d8ca025729234bb3416726667a0f2f75ae516918f879811dad3d7d1a2675ed605858ccfcf3b1a0934260b7a138

data/CHANGELOG.md

@@ -7,6 +7,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.3.1] - 2026-10-26
+
+### Fixed
+- Ruby 4.0 compatibility: `CCtx#compress`, `DCtx#decompress`, `VibeZstd.compress`/`.decompress`, and `CompressWriter#write` raised `FrozenError` when given a frozen string (including `# frozen_string_literal: true` literals). Ruby 4.0 refuses `rb_str_locktmp` on frozen strings; frozen input is already immutable, so the GVL-release lock added in 1.3.0 is now skipped for it. Unfrozen strings are still locked as before.
+
 ## [1.3.0] - 2026-06-11
 
 ### Security

data/ext/vibe_zstd/streaming.c

@@ -174,10 +174,15 @@ vibe_zstd_writer_write(VALUE self, VALUE data) {
     // Lock data for the duration of the compress loop so that RSTRING_PTR(data)
     // stays valid even when io.write (called inside the loop) runs Ruby code that
     // could otherwise mutate or resize the string.  rb_str_locktmp raises if the
-    // string is already locked; the ensure always unlocks it.
-    rb_str_locktmp(data);
-
+    // string is already locked; the ensure always unlocks it.  Frozen strings
+    // are already immutable and Ruby 4.0+ refuses to lock them, so skip it.
     vibe_zstd_write_state state = { cstream, data };
+    if (OBJ_FROZEN(data)) {
+        vibe_zstd_writer_write_body((VALUE)&state);
+        return self;
+    }
+
+    rb_str_locktmp(data);
     rb_ensure(vibe_zstd_writer_write_body, (VALUE)&state,
               vibe_zstd_writer_write_unlock, data);
 

data/ext/vibe_zstd/vibe_zstd.c

@@ -284,6 +284,10 @@ vibe_zstd_default_c_level(VALUE self) {
 // rb_thread_call_without_gvl can deliver a pending async exception (e.g.
 // Thread#raise, Timeout) after reacquiring the GVL, so the unlock must go
 // through rb_ensure or the string would be left permanently locked.
+//
+// Frozen strings are skipped: they cannot be mutated or resized, so the
+// pointer is already stable, and Ruby 4.0+ raises FrozenError from
+// rb_str_locktmp on a frozen string.
 typedef struct {
     void* (*func)(void*);
     void* arg;
@@ -305,6 +309,10 @@ nogvl_locked_unlock(VALUE str) {
 static void
 vibe_zstd_nogvl_with_str_locked(void* (*func)(void*), void* arg, VALUE str) {
     nogvl_locked_call call = { func, arg };
+    if (OBJ_FROZEN(str)) {
+        nogvl_locked_body((VALUE)&call);
+        return;
+    }
     rb_str_locktmp(str);
     rb_ensure(nogvl_locked_body, (VALUE)&call, nogvl_locked_unlock, str);
 }

data/lib/vibe_zstd/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module VibeZstd
-  VERSION = "1.3.0"
+  VERSION = "1.3.1"
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: vibe_zstd
 version: !ruby/object:Gem::Version
-  version: 1.3.0
+  version: 1.3.1
 platform: ruby
 authors:
 - Kelley Reynolds
 bindir: exe
 cert_chain: []
-date: 2026-06-12 00:00:00.000000000 Z
+date: 2026-10-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: benchmark-ips