nosj 0.5.0-aarch64-linux → 0.5.1-aarch64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8bd202a41866bf66ced093153a4a0ca1166ed3a2dc495eaa8189d0a6e6b58aa7
-  data.tar.gz: 8c7c12413a1bff0d9ff9d72d5629700e14a5c922fd1790ebe2ec46879be45d25
+  metadata.gz: 646d09f639df7ba42e96c2868d4928fc5220f012e89e71cbf5448c4baab01a67
+  data.tar.gz: 997a0090725c47ca01f1236b7e5359a76f6bdee8b0ed97bbd975e9b19eb2c98f
 SHA512:
-  metadata.gz: 045b0214d996b133b5c99ec958d5f929f12adf7e134671c9ff70895a4168d9a6a7ce78c261d6d8c5453b38af7363ded4a918b9d5fbb6c50dd8b06b15283de4af
-  data.tar.gz: d8717b79f4bddf22206fa248e57521282be0f197210683724adb8f831adf5a26581dd92e9d0192e3973070252f5acdc2968e6f8686ea5c916ebc5387a72602bc
+  metadata.gz: 35c39edf12ae12d52af9628f2b0bde5ae7aedb6d1102e8ddbea71bb04cb042356fa1e210cd969c0df47d4e9cc0dab3b698dd5ccf4eddf81e06b2df6a7c00db85
+  data.tar.gz: 94dfb574a6bf209c912d7933aec524bd0ce5b67cc537294ba85f21c1b28f4952bfb48516f63279ac84d01ab89217ceb7231ce54941fdfc5427e109306ee02419

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: aarch64-linux
 authors:
 - Yaroslav Markin