This repository has been archived by the owner on Aug 14, 2024. It is now read-only.
New version of json (2.6.0) broke the build #85
Closed
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.6.0) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 34 commits:
Bump up json version to 2.6.0
Merge pull request #473 from flori/cleanup
Use Gemfile instead of Gem::Specification#add_development_dependency
Removed needless files from gemspec
Merge pull request #471 from flori/fix-actions
Merge pull request #469 from nobu/fix-ragel-warnings
Try to enable Windows with Ruby 3.0
Removed mswin and mingw because they are broken now
Removed debug environment
Update the status badge for CI
parser: fix warnings against code generated by ragel
Merge pull request #467 from kamipo/fix_typos
Fix some typos
Fix GC compatibility: Don't stash encodings in global constants
Removed executable bit
Merge pull request #461 from ybiquitous/patch-1
Bump version of required_ruby_version to 2.3. Fixes #464
Merge pull request #451 from Shopify/ruby-interned-str
Deduplicate strings inside json_string_unescape
Refactor json_string_unescape
Merge pull request #463 from mrkn/github_actions
CI: Specify the version 3.0 as a String
CI: Install ragel on Ubuntu
CI: Install ragel on macOS
CI: Use GitHub Actions for CI
CI: Stop using Travis CI
Use better condition for the old ruby versions
CI: Specify the version 3.0 as a String
CI: Install ragel on Ubuntu
CI: Install ragel on macOS
CI: Use GitHub Actions for CI
CI: Stop using Travis CI
Added helper task for test suite sync
Fix incorrect `#` position in API doc
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