New version of json (2.7.2) broke the build #150
Conversation
This file contains 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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
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.
We've tested your project with an updated dependency and the build failed.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.
If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)
We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of json for this test run.
What changed?
✳️ json (>= 1.8.0 → 2.7.2) · Repo · Changelog
Release Notes
2.7.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
Bump up 2.7.2Merge pull request #578 from flori/warn-bundled-gemsWarn to install ostruct if json couldn't load itMerge pull request #577 from tompng/autoload_generic_objectMerge pull request #576 from headius/no_19_jruby_methodsAutoload GenericObject to avoid require ostruct warning in Ruby 3.4Remove references to "19" methods in JRubyMerge pull request #575 from flori/refine-ciExclude 2.3-2.5 on macos-14 iamgeAdded JRuby 9.4TruffleRuby 24 is brokenAdded latest stable versions of macOSmacOS 11 is EOL todayMerge pull request #574 from peterzhu2118/generator-mem-leakFix memory leak when exception is raised during JSON generationMerge pull request #571 from mperham/patch-1Update README.mdMerge pull request #565 from flori/optional-ostructMake OpenStruct support as optionalMerge pull request #561 from jhawthorn/rb_sym2strUse rb_sym2str instead of SYM2ID