Keep JSON parsing compatible with supported Ruby 3.1 #89

Fresh dependency resolution on supported Ruby 3.1 selects multi_json 1.19.1 and json 3.1.0. MultiJson passes a second positional parsing-options argument, while JSON 3 accepts keyword options, so decoding any response raises ArgumentError: wrong number of arguments (given 2, expected 1).

Reproduced independently of SDK code on Ruby 3.1.0:

require 'multi_json'
require 'json'
puts MultiJson::VERSION # 1.19.1
puts JSON::VERSION      # 3.1.0
MultiJson.load('{"ok":true}')
# json/common.rb:291:in `parse': wrong number of arguments (given 2, expected 1)

transloadit.gemspec on main (79535b2) has no JSON version bound. This breaks the Ruby 3.1 CI job and real consumers even though the gem supports Ruby >= 3.1.

Constrain JSON to < 3.0 while Ruby 3.1 resolves this MultiJson version, or adopt a parser combination that supports both. The same dependency bound is already included in open PRs #84, #85, #86 and #87. Keep this issue as a standalone record of the dependency failure, found during #88 validation.

Compatibility constraint: an unconditional runtime json < 3.0 bound also rejects working Ruby >= 3.2 applications that require JSON 3. MultiJson 1.21.2 supports JSON 3, but requires Ruby >= 3.2. The eventual runtime fix should preserve that compatible combination.

The #88 change keeps this independent runtime issue open: only the repository's Ruby 3.1 test bundle is constrained to JSON 2, and the README documents the same application workaround. A consumer bundle requiring JSON >= 3 on Ruby 4.0 was confirmed to fail under the global cap and pass the full suite once that runtime cap was removed.

_{🤖 Released by kvz on framework1/ruby-sdk since 2026-10-18 · resume: codex resume 01a14e1d-ce02-76b1-81f0-5014b90ba94d}