nosj 0.5.0-x86_64-linux → 0.5.1-x86_64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0c308d0f2486a7041e62e8c1de75a7711429d59e4cd4cbc646345ad09d4eef83
-  data.tar.gz: 5a6d0a7476cf09997f7234e404e78bd9f4c25b9b4444cdaf9116a52c5f4c392f
+  metadata.gz: 8de4a4280aa43d113a6a7d51ce10a7a8702c9e4652c6867a3cf4486abb55f7e7
+  data.tar.gz: e9349c8cdf8252e703db35d4d7aabb04470fe6ae7bd11533e4b98683f19aa1c2
 SHA512:
-  metadata.gz: f2d87102fd15520c3183daf859329eb1c1f92ff81e73112d0882e5f8fde8138e3751a083513206381431e1af0f2ffe12a01bd8176aca1b4ce9be01707d57f7a7
-  data.tar.gz: 4c70d1d907f4a9db68cb02d4231f8258ac9780f4b8bbf935383dedaf0490e5686bd32812234cb5d32599bc26335854fe19e9c5fd1d9c384de61cdbf1f494d4e7
+  metadata.gz: 9c289bcfc3b32cbdb53fe924c380e4256c73d9386516078682d6d7ac90f42e1a89c454bb2afe0867fb26b51e8f223350806daeaca8dcd9559974f57291966e41
+  data.tar.gz: b978a9d15969408548a5bc30ac41d29d93cf090826a578bff1912bcd3a5c9d9e33125e65c92e03b69d1f9c63ed0458690860136c41537b034f37a9d0a070fa60

data/CHANGELOG.md

@@ -1,3 +1,13 @@
+## [0.5.1] - 2026-10-06
+
+- Fixed: `NOSJ.patch` read a `path` without the leading slash (`"a"`
+  instead of `"/a"`) as the root pointer, so `add`, `copy`, and `move`
+  silently replaced the whole document with the value instead of
+  raising, and `remove` reported `cannot remove the root`. Such paths
+  now raise the same `ArgumentError` as `NOSJ.at_pointer`
+  (`JSON Pointer must be empty or start with '/'`) in every op. The
+  bug dates back to 0.3.0. Found by fuzzing.
+
 ## [0.5.0] - 2026-09-25
 
 **json 3.0 compatibility.** nosj now matches the behavior of the json

data/lib/nosj/version.rb

@@ -2,5 +2,5 @@
 
 module NOSJ
   # The gem version.
-  VERSION = "0.5.0"
+  VERSION = "0.5.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: nosj
 version: !ruby/object:Gem::Version
-  version: 0.5.0
+  version: 0.5.1
 platform: x86_64-linux
 authors:
 - Yaroslav Markin