Update oj 3.16.16 → 3.16.17 (patch)#681
Merged
depfu[bot] merged 1 commit intodevelopfrom Apr 19, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #681 +/- ##
========================================
Coverage 81.16% 81.16%
========================================
Files 75 75
Lines 1237 1237
========================================
Hits 1004 1004
Misses 233 233
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ oj (3.16.16 → 3.16.17) · Repo · Changelog
Release Notes
3.16.17
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 11 commits:
Update changelogUpdate changelogRaise error for incomplete primitive literals (#1005)Fix read() not handling partial reads for large files (#1004)Handle unterminated strings in usual parser (#1002)Bump jidicula/clang-format-action from 4.17.0 to 4.18.0 (#1001)Array hash as json (#1003)Update changelog to unreleasedAddress issue #985Bump jidicula/clang-format-action from 4.15.0 to 4.17.0 (#999)Use fast_memcpy16 to quickly copy up to 16 bytes to for tail handing in ARM Neon code. (#998)Release Notes
4.1.2
4.1.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 24 commits:
Bump version to v4.1.2 (#529)Update dtoa to version from Ruby 4.0 (#528)Merge pull request #526 from ruby/dependabot/github_actions/step-security/harden-runner-2.17.0Bump step-security/harden-runner from 2.16.1 to 2.17.0Fix unary minus on unsigned type warning (#525)BigMath.exp overflow/underflow check (#523)Revert "Add a workaround for slow BigDecimal#to_f when it has large N_significant_digits (#514)" (#522)Use '0'+n for converting single digit to char (#521)Merge pull request #517 from ruby/dependabot/github_actions/rubygems/release-gem-1.2.0Merge pull request #518 from ruby/dependabot/github_actions/step-security/harden-runner-2.16.1Fix calloc-transposed-args warning (#520)Optimize BigDecimal#to_s (#519)Bump step-security/harden-runner from 2.16.0 to 2.16.1Bump rubygems/release-gem from 1.1.4 to 1.2.0Bump version to v4.1.1 (#516)Add a workaround for slow BigDecimal#to_f when it has large N_significant_digits (#514)tiny grammar fix in README.md (#513)Update to cover change in Bundler (#512)Increase VpMult batch size (#511)Multiplication with 8-decdig batch (#501)Remove unused minitest from Gemfile (#510)Make BigDecimal object embedded (#507)Add changelog for 4.1.0. (#508)Define `test` as the default rake task (#509)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