Upgrade json to version 2.4.0 #16
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.4) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 47 commits:
Bump version to 2.4.0SortedSet was removed at a3db08d7b6ff119223f77e3df00b4f6deac971e2Merge pull request #450 from flori/backport-ruby-coreDrop to support Ruby 2.0t/json/json_common_interface_test.rb: fix wrong indentationRemove unneeded `begin` and `end`Fix `Leaked tempfile`sExtract assert assertion to assert_include and assert_not_include.assert_true is not provided by test-unitRemove unnecessary executable bit [ci skip]test/json/json_parser_test.rb: suppress warningsstrip trailing spaces [ci skip]Complex and Rational is embedded classes nowMerge pull request #447 from Shopify/global-freeze-optionMerge pull request #449 from chrisseaton/pretty-emptyFix an issue with generate_pretty and empty objects in the Ruby and Java implementationsImplement a freeze: parser optionMerge pull request #448 from Shopify/fix-load-file-docFix JSON.load_file docMerge pull request #446 from BurdetteLamar/rdocPartial compliance with doc/method_documentation.rdocMerge pull request #425 from marcandre/fix_pure_parserEnhanced RDoc for JSON.dump (#443)Merge pull request #444 from jfeltesse-mdsol/fix/licensebundle the LICENSE file in the gemMerge pull request #405 from Shopify/escape-slash-2.3.0Merge pull request #442 from BurdetteLamar/rdocNodoc for recurse_procMerge pull request #439 from BurdetteLamar/masterRDoc for JSON.load with procMerge pull request #436 from kares/green-ci[test] properly 'skip' test on JRubyMerge pull request #435 from kares/jruby-sync[refactor] drop old JRuby 1.7 compat codeunify json-java gemspec with the baselineMerge pull request #434 from BurdetteLamar/masterRDoc example for JSON.loadMerge pull request #385 from nobu/bug/non-utf8Merge pull request #372 from kares/jruby-ciMerge pull request #433 from BurdetteLamar/masterAdd an option to escape forward slash characterEnhance RDoc for JSON.parseMerge pull request #432 from mame/prevent-warning-during-testtest/json/json_fixtures_test.rb: Prevent an "out of range" warningMerge pull request #431 from mame/avoid-relative-path-in-load-pathDo not add a relative path to $LOAD_PATHMerge pull request #430 from BurdetteLamar/master👉 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:
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