Update oj 3.16.6 → 3.16.12 (patch) #179
Open
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.6 → 3.16.12) · Repo · Changelog
Release Notes
3.16.12
3.16.11 (from changelog)
3.16.10 (from changelog)
3.16.9 (from changelog)
3.16.8 (from changelog)
3.16.7 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 38 commits:
Fix clang format issuesUpdate changelogFix buffer realloc issueImprove worst case performance when using ARM Neon instructions (#970)Restore TruffleRuby in CI (#972)Fix spelling errorUpdate changelog`size_t` everywhere. (#969)ARM Neon optimization of `oj_dump_cstr` (#967)Optimize rails_xss_friendly_size and rails_friendly_size with ARM Neon instructions. (#966)Increment the str pointer. (#965)clang-format fixesCircular range (#964)Use ARM Neon instructions to accelerate hibit_friendly_size. (#963)Bump jidicula/clang-format-action from 4.14.0 to 4.15.0 (#960)Fix typo of "escaping" (#959)Release preparationExpose `oj_parser_type` for extensions (#958)CI: Fix failures with Ruby 3.5-dev (#957)github: add 3.4 for CI (#956)Mention drop of Ruby 2.6 in OJ 3.14.3 (#954)Remove broken rails 7 from CIRemove test files to reduce gem size (#952)Use rb_utf8_str_new/rb_utf8_str_new_cstr to create UTF8 string (#950)bench: Avoid allocating an extra hash when not necessary (#949)Improve performance of reading escaped string (#948)CI: Add Rails 8 and drop Rails 6.1 (#947)Fixed Oj::Parser create_id size issue #931Bump jidicula/clang-format-action from 4.13.0 to 4.14.0 (#942)Sort the conditional statements (#946)Release prepFix streaming to file descriptor (#945)Update changelogProperly declare global variables (#941)Allow more option in test resultUpdate changelogComment out truffleruby on CIWIPRelease Notes
3.3.1
3.3.0
3.2.3
3.2.2
3.2.1
3.2.0
3.1.9 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
0.6.3
0.6.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 23 commits:
v0.6.3use `Ractor.shareable_proc`Bump step-security/harden-runner from 2.12.1 to 2.12.2v0.6.2Bump step-security/harden-runner from 2.12.0 to 2.12.1 (#80)Don't need to use admin secret for gh releaseUse `Ractor#value` as `Ractor#take` is removedBump step-security/harden-runner from 2.11.1 to 2.12.0Bump step-security/harden-runner from 2.11.0 to 2.11.1Bump step-security/harden-runner from 2.10.4 to 2.11.0Bump step-security/harden-runner from 2.10.3 to 2.10.4Bump step-security/harden-runner from 2.10.2 to 2.10.3 (#71)Provide a 'Changelog' link on rubygems.org/gems/ostructBump rubygems/release-gem from 1.1.0 to 1.1.1Fixed version number of rubygems/release-gemBump rubygems/release-gemBump step-security/harden-runner from 2.10.1 to 2.10.2Exclude TruffleRuby from Actions. It easily broke our CICI: Run Ruby 2.5 on macos-13 (#64)Bump up v0.6.1Enabled trusted publisher for rubygems.orgUpdate license files same as ruby/rubyDo not include a backtick in error messages and backtracesDepfu 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