Make multi_json compatible with json 3.x

[byroot]

Ref: https://github.com/ruby/json/releases/tag/v3.0.0.rc1

Unknown keyword arguments will raise ArgumentError.

• quirks_mode: no longer existing since json 2.0 (~2011).
• create_additions no longer existing in json 3.0.

NB: rubocop prevent installing the RC, so I only did some local testing after messing with the Gemfile.

[sferik]

To handle RuboCop preventing json 3 from being installed, what would you think about moving the linters into a group :lint and adding a test matrix job that runs with bundle config set --local without lint and an unpinned json gem? Happy to do that in a separate PR if you'd prefer.

[byroot]

what would you think about moving the linters into a group :lint

I don't thin that would be enough, as the constraints would still apply.

I did submit a PR to rubocop which was merged, hopefully it's released soon.

[byroot]

@sferik sorry to be a bother, but could I request a new release? I released json 3.0.0 this morning, and now a few projects test suites are broken as they need a new version of multi_json.

[vpellan]

Hello! Sincemulti_json 1.20+ is only compatible with Ruby 3.2+, can this fix be backported tomulti_json 1.19 branch? Both multi_json 1.19 and json 3 are compatible with Ruby 3.0/3.1 but multi_json 1.19 gemspec does not prevent json 3+

[sferik]

@byroot No bother. I will cut a new multi_json release this morning.

@vpellan Can you say a bit more about why you’d like support for Ruby 3.0 and 3.1? As you’re probably aware, support for Ruby 3.0 ended over 2 years ago. There are several known security vulnerabilities that are unpatched in the latest 3.0.7 and 3.1.7 releases. If it’s important to you to run the latest version of json/multi_json, I’d expect you’d also be interested to upgrade your Ruby version to one that is still supported.

If I go ahead with this backport, how much longer would you expect me to support Ruby 3.0 and 3.1? The json gem still supports Ruby 2.7, which has been EOL for over three years. Would you expect multi_json to support that version as well? I hope you are not offended by me mentioning this, but would @DataDog be interested in sponsoring this work? Generally speaking, long-term support for EOL versions requires a corporate sponsor.

[sferik]

Shipped!