Update sentry-rails 5.18.0 → 5.19.0 (minor)

[depfu]

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?

✳️ sentry-rails (5.18.0 → 5.19.0) · Repo · Changelog

Release Notes

5.19.0

Features

• Use Concurrent.available_processor_count instead of Concurrent.usable_processor_count (#2358)

• Support for tracing Faraday requests (#2345)

  • Closes #1795
  • Please note that the Faraday instrumentation has some limitations in case of async requests: lostisland/faraday#1381
  • lostisland/faraday#1381

  Usage:

  Sentry.init do |config|
    # ...
    config.enabled_patches << :faraday
  end

• Support for attachments (#2357)

  Usage:

  Sentry.add_attachment(path: '/foo/bar.txt')
  Sentry.add_attachment(filename: 'payload.json', bytes: '{"value": 42}'))

• Transaction data are now included in the context (#2365)

  • Closes #2364

• Inject Sentry meta tags in the Rails application layout automatically in the generator (#2369)

  To turn this behavior off, use

  bin/rails generate sentry --inject-meta false

Bug Fixes

• Fix skipping connect spans in open-telemetry #2364

5.18.2

Bug Fixes

• Don't overwrite ip_address if already set on user #2350
  • Fixes #2347
• teardown_sentry_test helper should clear global even processors too (#2342)
• Suppress the unnecessary “unsupported options notice” (#2349)

Internal

• Use Concurrent.usable_processor_count when it is available (#2339)
• Report dropped spans in Client Reports (#2346)

5.18.1

Bug Fixes

• Drop Gem::Specification's usage so it doesn't break bundler standalone (#2335)

Does any of this look wrong? Please let us know.

✳️ sentry-ruby (5.18.0 → 5.19.0) · Repo · Changelog

Release Notes

5.18.2

Bug Fixes

• Don't overwrite ip_address if already set on user #2350
  • Fixes #2347
• teardown_sentry_test helper should clear global even processors too (#2342)
• Suppress the unnecessary “unsupported options notice” (#2349)

Internal

• Use Concurrent.usable_processor_count when it is available (#2339)
• Report dropped spans in Client Reports (#2346)

5.18.1

Bug Fixes

• Drop Gem::Specification's usage so it doesn't break bundler standalone (#2335)

Does any of this look wrong? Please let us know.

↗️ concurrent-ruby (indirect, 1.3.3 → 1.3.4) · Repo · Changelog

Release Notes

1.3.4

What's Changed

• Update comment for JRuby variant of processor_count to reality by @meineerde in #1054
• Add Concurrent.cpu_requests that is cgroups aware. by @heka1024 in #1058
• Fix the doc of Concurrent.available_processor_count by @y-yagi in #1059
• Fix the return value of Concurrent.available_processor_count when cpu.cfs_quota_us is -1 by @y-yagi in #1060

New Contributors

• @heka1024 made their first contribution in #1058
• @y-yagi made their first contribution in #1059

Full Changelog: v1.3.3...v1.3.4

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 10 commits:

• Avoid requiring files of the gem in Rakefile to avoid redefined method warnings
• Avoid require in Gemfile & Rakefile to avoid redefined constant warnings
• Avoid require in *.gemspec files to avoid redefined constant warnings
• Update docs-source/signpost.md
• 1.3.4
• Check early that $CONCURRENT_JRUBY_HOME is set
• Fix the return value of `Concurrent.available_processor_count` when `cpu.cfs_quota_us` is -1
• Fix the doc of `Concurrent.available_processor_count`
• Add `Concurrent.cpu_shares` that is cgroups aware.
• Update comment for JRuby variant of processor_count to reality

↗️ minitest (indirect, 5.24.1 → 5.25.0) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 21 commits:

• prepped for release
• + Refactored siginfo handler to reduce runtime costs. Saved ~30%!
• normalized all actual/expected var names for assert_equal tests
• Accept colon style Hash#inspect in test. (tompng)
• - Improve description of test:slow task. (stomar)
• - Cleaning up ancient code checking for defined?(Encoding) and the like.
• Minor fix to make deprecation tests pass when using rake testW0
• oops
• + Fixed some inefficiencies filtering and matching (mostly backtraces).
• More foolish consistency...
• More foolish consistency... "So many parens!" edition
• More foolish consistency...
• "A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers and divines"—Emerson
• - Disambiguated some shadowed variables in minitest/compress.
• Got rid of ANCIENT pre-Integer-merge tests
• Got rid of ANCIENT RUBY18 conditioned tests
• - Fixed an ironic bug if using string-literals AND Werror.
• Finally removed all clean + heredoc for squiggly heredocs in test.
• - Added missing rdoc to get back to 100% coverage.
• Double quoted some (ancient) string literals.
• Fixed 3 tests when using minitest-gcstats.

↗️ nokogiri (indirect, 1.16.6 → 1.16.7) · Repo · Changelog

Release Notes

1.16.7

v1.16.7 / 2024-07-27

Dependencies

• [CRuby] Vendored libxml2 is updated to v2.12.9, which the upstream release notes state is a security release to address CVE-2024-40896. Nokogiri's maintainers believe this vulnerability does not affect users of Nokogiri, but we advise upgrading at your earliest convenience anyway.

---

sha256 checksums:

78778d35f165b59513be31c0fe232c63a82cf97626ffba695b5f822e5da1d74b  nokogiri-1.16.7-aarch64-linux.gem
c84cdb9e3aa44c35bbb981b20175838c4b2066c26c5cb118f31f177168a42fc3  nokogiri-1.16.7-arm-linux.gem
276dcea1b988a5b22b5acc1ba901d24b8e908c40b71dccd5d54a2ae279480dad  nokogiri-1.16.7-arm64-darwin.gem
044c45ca46abc2b6135a85ab39a546ff2f0434d43142bc59b83e5b1068876a42  nokogiri-1.16.7-java.gem
01ed785392f9cbdfd45e0e5ef6ad6d2c80a6128672589448f18952168bd68e56  nokogiri-1.16.7-x64-mingw-ucrt.gem
d8fd5c675743b85354c9098117bfa9e703c7cacab8c33e5190104ea8218ad1ec  nokogiri-1.16.7-x64-mingw32.gem
dddbf1c1ef99ce9fab98302b14f8bacb703e6f16e89b99f05ecee8a1fca23664  nokogiri-1.16.7-x86-linux.gem
b6517d995b024739cbb81251a26866d40e1ccb151936b5bb0977e7487f4e617c  nokogiri-1.16.7-x86-mingw32.gem
630732b80fc572690eab50c73a1f18988f3ac401ed0b67ca9956ba2b1e2c3faa  nokogiri-1.16.7-x86_64-darwin.gem
9e1e428641d5942af877c60b418c71163560e9feb4a5c4015f3230a8b86a40f6  nokogiri-1.16.7-x86_64-linux.gem
f819cbfdfb0a7b19c9c52c6f2ca63df0e58a6125f4f139707b586b9511d7fe95  nokogiri-1.16.7.gem

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 3 commits:

• version bump to v1.16.7
• dep: update libxml2 to v2.12.9 (branch v1.16.x) (#3297)
• dep: update packaged libxml2 to v2.12.9

↗️ racc (indirect, 1.8.0 → 1.8.1) · Repo · Changelog

Release Notes

1.8.1

What's Changed

• Use require_relative in the Racc codebase by @koic in #269
• Fix a typo by @koic in #270
• Provide a 'Changelog' link on rubygems.org/gems/racc by @mark-young-atg in #271
• Fix RDoc main file to "README.rdoc" by @ydah in #274
• Fix file path and line number errors when using +, * and () by @ydah in #273
• Bump up v1.8.1 by @yui-knk in #275

New Contributors

• @koic made their first contribution in #269
• @mark-young-atg made their first contribution in #271

Full Changelog: v1.8.0...v1.8.1

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 15 commits:

• Merge pull request #275 from yui-knk/v1.8.1
• Bump up v1.8.1
• Merge pull request #273 from ydah/fix-filepath-lineno
• Add test code for TestRaccCommand
• Fix file path and line number errors when using `+`, `*` and `()`
• Merge pull request #274 from ydah/rename-docs-main
• Fix RDoc main file to "README.rdoc"
• Merge pull request #271 from mark-young-atg/provide_changelog_link_on_rubygems
• Provide a 'Changelog' link on rubygems.org/gems/racc
• Merge pull request #270 from koic/fix_a_typo
• Fix a typo
• Added BSDL to gemspec
• Update license files same as ruby/ruby
• Merge pull request #269 from koic/use_require_relative
• Use `require_relative` in the Racc codebase

↗️ zeitwerk (indirect, 2.6.16 → 2.6.17) · Repo · Changelog

Release Notes

2.6.17 (from changelog)

• Fix log message when eager loading a directory ends.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 2 commits:

• Ready for 2.6.17
• Fix log message when eager loading a directory ends

---

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

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[coveralls]

coverage: 98.313%. remained the same
when pulling a98ee06 on depfu/update/group/sentry-ruby-core-5.19.0
into 38aeb7d on main.

[depfu]

Closing because this update has already been applied