Upgrade json to version 2.3.1

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ json (~> 1.7 → ~> 2.3) · Repo · Changelog

Release Notes

2.3.1 (from changelog)

• Spelling and grammar fixes for comments. Pull request #191 by Josh Kline.
• Enhance generic JSON and #generate docs. Pull request #347 by Victor Shepelev.
• Add :nodoc: for GeneratorMethods. Pull request #349 by Victor Shepelev.
• Baseline changes to help (JRuby) development. Pull request #371 by Karol Bucek.
• Add metadata for rubygems.org. Pull request #379 by Alexandre ZANNI.
• Remove invalid JSON.generate description from JSON module rdoc. Pull request #384 by Jeremy Evans.
• Test with TruffleRuby in CI. Pull request #402 by Benoit Daloze.
• Rdoc enhancements. Pull request #413 by Burdette Lamar.
• Fixtures/ are not being tested... Pull request #416 by Marc-André Lafortune.
• Use frozen string for hash key. Pull request #420 by Marc-André Lafortune.
• Added :call-seq: to RDoc for some methods. Pull request #422 by Burdette Lamar.
• Small typo fix. Pull request #423 by Marc-André Lafortune.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 54 commits:

• Bump version to 2.3.1
• Merge pull request #429 from flori/remove-generate-task-for-gemspec
• Removed gemspec task from default task on Rakefile
• Use VERSION file instead of hard-coded value
• Removed explicitly date field in gemspec, it will assign by rubygems.org
• Removed task for json_pure.gemspec
• Merge pull request #426 from marcandre/indent
• Merge pull request #428 from marcandre/change_fix
• Make changes more precise [#424]
• Merge pull request #424 from marcandre/update_changes
• Fix alignment
• Merge pull request #423 from marcandre/typo
• Update Changes for 2.3.0 [Fixes #397]
• Typo fix
• Merge pull request #422 from BurdetteLamar/master
• Added :call-seq: to RDOc for some methods
• Merge pull request #413 from BurdetteLamar/master
• Merge pull request #420 from marcandre/performance_345
• Use frozen string for hash key
• RDoc enhancements
• RDoc enhancements
• RDoc enhancements
• Merge pull request #418 from nobu/sync-ruby
• Removed nonsense `rubygems_version` in input gemspec files
• ext/json/parser/prereq.mk: remove type-limit warning if char is unsigned
• ext/json/parser/prereq.mk: Add a "automatically generated" header
• Merge pull request #415 from marcandre/cleanup
• Merge pull request #416 from marcandre/red_green_please
• Fix test that wasn't testing anything
• Merge pull request #371 from kares/jruby-baseline
• Fix rake task description
• Accept test-unit v3.x too
• Update gemspec.
• Add comment that gemspec is generated automatically
• Merge pull request #191 from jkanywhere/spell-fixes
• Rdoc enhancements
• Merge pull request #402 from eregon/patch-1
• Add truffleruby in allow_failures as requested
• Test with TruffleRuby in CI
• Merge pull request #347 from zverok/enhance-docs
• Merge pull request #379 from noraj/patch-1
• add metadata
• Fix examples syntax
• Enchance generic JSON and #generate docs
• Merge pull request #349 from zverok/nodoc
• Merge pull request #398 from flori/update-gemspec
• Added instruction to Relase section
• Removed gemspec_ext from gemspec task because it always add control char to gemspec.
• Gem::Specification#date is set automatically by RubyGems.org.
• Restore json.gemspec from 619a85865db3714b989cbc8bc097af631cad9a9f
• Merge pull request #384 from jeremyevans/json-generate-doc-fix
• Merge pull request #396 from flori/update-requirement
• keyword argument is provided after Ruby 2.0+
• Add procedure of releasing a gem

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #16.