Update sentry-rails 5.23.0 → 5.24.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.23.0 → 5.24.0) · Repo · Changelog

Release Notes

5.24.0

Features

• Add new sidekiq config report_only_dead_jobs (#2581)

• Add max_nesting of 10 to breadcrumbs data serialization (#2583)

• Add sidekiq config propagate_traces to control trace header injection (#2588)

  If you use schedulers you can get one large trace with all your jobs which is undesirable.
  We recommend using the following to propagate traces only from the Rails server and not elsewhere.

  config.sidekiq.propagate_traces = false unless Rails.const_defined?('Server')

• Only expose active_storage keys on span data if send_default_pii is on (#2589)

• Add new Sentry.logger for Structured Logging feature (#2620).

  To enable structured logging you need to turn on the enable_logs configuration option:

  Sentry.init do |config|
    # ... your setup ...
    config.enable_logs = true
  end

  Once you configured structured logging, you get access to a new Sentry.logger object that can be
  used as a regular logger with additional structured data support:

  Sentry.logger.info("User logged in", user_id: 123)
  Sentry.logger.error("Failed to process payment",
  
  transaction_id: "tx_123",
  
  error_code: "PAYMENT_FAILED"
  
  )

  You can also use message templates with positional or hash parameters:

  Sentry.logger.info("User %{name} logged in", name: "Jane Doe")
  Sentry.logger.info("User %s logged in", ["Jane Doe"])

  Any other arbitrary attributes will be sent as part of the log event payload:

  # Here `user_id` and `action` will be sent as extra attributes that Sentry Logs UI displays
  Sentry.logger.info("User %{user} logged in", user: "Jane", user_id: 123, action: "create")

  ⚠️ When enable_logs is true, previous Sentry.logger should no longer be used for internal SDK
  logging - it was replaced by Sentry.configuration.sdk_logger and should be used only by the SDK
  itself and its extensions.

• New configuration option called active_job_report_on_retry_error which enables reporting errors on each retry error (#2617)

Bug Fixes

• Gracefully fail on malformed utf-8 breadcrumb message (#2582)
  • Fixes #2376
• Fix breadcrumb serialization error message to be an object (#2584)
  • Fixes #2478
• Fix compatibility issues with sidekiq-cron 2.2.0 (#2591)
• Update sentry-sidekiq to work correctly with Sidekiq 8.0 and its new timestamp format (#2570)
• Ensure we capture exceptions after each job retry (#2597)

Internal

• Remove user_segment from DSC (#2586)
• Replace logger with sdk_logger (#2621)
• Sentry.logger is now deprecated when enable_logs is turned off. It's original behavior was ported to Sentry.configuration.sdk_logger. Please notice that this logger is internal and should only be used for SDK-specific logging needs. (#2621)

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

✳️ sentry-ruby (5.23.0 → 5.24.0) · Repo · Changelog

Release Notes

5.24.0

Features

• Add new sidekiq config report_only_dead_jobs (#2581)

• Add max_nesting of 10 to breadcrumbs data serialization (#2583)

• Add sidekiq config propagate_traces to control trace header injection (#2588)

  If you use schedulers you can get one large trace with all your jobs which is undesirable.
  We recommend using the following to propagate traces only from the Rails server and not elsewhere.

  config.sidekiq.propagate_traces = false unless Rails.const_defined?('Server')

• Only expose active_storage keys on span data if send_default_pii is on (#2589)

• Add new Sentry.logger for Structured Logging feature (#2620).

  To enable structured logging you need to turn on the enable_logs configuration option:

  Sentry.init do |config|
    # ... your setup ...
    config.enable_logs = true
  end

  Once you configured structured logging, you get access to a new Sentry.logger object that can be
  used as a regular logger with additional structured data support:

  Sentry.logger.info("User logged in", user_id: 123)
  Sentry.logger.error("Failed to process payment",
  
  transaction_id: "tx_123",
  
  error_code: "PAYMENT_FAILED"
  
  )

  You can also use message templates with positional or hash parameters:

  Sentry.logger.info("User %{name} logged in", name: "Jane Doe")
  Sentry.logger.info("User %s logged in", ["Jane Doe"])

  Any other arbitrary attributes will be sent as part of the log event payload:

  # Here `user_id` and `action` will be sent as extra attributes that Sentry Logs UI displays
  Sentry.logger.info("User %{user} logged in", user: "Jane", user_id: 123, action: "create")

  ⚠️ When enable_logs is true, previous Sentry.logger should no longer be used for internal SDK
  logging - it was replaced by Sentry.configuration.sdk_logger and should be used only by the SDK
  itself and its extensions.

• New configuration option called active_job_report_on_retry_error which enables reporting errors on each retry error (#2617)

Bug Fixes

• Gracefully fail on malformed utf-8 breadcrumb message (#2582)
  • Fixes #2376
• Fix breadcrumb serialization error message to be an object (#2584)
  • Fixes #2478
• Fix compatibility issues with sidekiq-cron 2.2.0 (#2591)
• Update sentry-sidekiq to work correctly with Sidekiq 8.0 and its new timestamp format (#2570)
• Ensure we capture exceptions after each job retry (#2597)

Internal

• Remove user_segment from DSC (#2586)
• Replace logger with sdk_logger (#2621)
• Sentry.logger is now deprecated when enable_logs is turned off. It's original behavior was ported to Sentry.configuration.sdk_logger. Please notice that this logger is internal and should only be used for SDK-specific logging needs. (#2621)

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

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

Release Notes

1.3.5

What's Changed

• Remove dependency on logger by @eregon in #1062
• Avoid error when member is present on ancestor class by @francesmcmullin in #1068
• Set rake-compiler source and target to Java 8 by @headius in #1071
• chore: fix typos by @chenrui333 in #1076

New Contributors

• @francesmcmullin made their first contribution in #1068
• @chenrui333 made their first contribution in #1076

Full Changelog: v1.3.4...v1.3.5

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

Commits

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

• Release concurrent-ruby 1.3.5 and concurrent-ruby-edge 0.7.2
• chore: fix typos (#1076)
• Set rake-compiler source and target to Java 8 (#1071)
• Improve ancestor classes spec
• Avoid error when member is present on ancestor class
• Remove dependency on logger

↗️ loofah (indirect, 2.24.0 → 2.24.1) · Repo · Changelog

Release Notes

2.24.1

2.24.1 / 2025-05-12

Ruby support

• Import only what's needed from cgi for support for Ruby 3.5 #296 @Earlopain

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

Commits

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

• version bump to v2.24.1
• Merge pull request #297 from flavorjones/flavorjones/ci-matrix-202505
• ci: add jruby 10 and jruby head, bump ruby versions for jobs
• Merge pull request #296 from Earlopain/cgi-ruby-3.5
• Only load what is required from `cgi`

↗️ mini_portile2 (indirect, 2.8.8 → 2.8.9) · Repo · Changelog

Release Notes

2.8.9

2.8.9 / 2025-05-12

Ruby support

• Import only what's needed from cgi, for supporting Ruby 3.5. #160 @Earlopain

New Contributors

• @kenhys made their first contribution in #156
• @Earlopain made their first contribution in #160

Full Changelog: v2.8.8...v2.8.9

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

Commits

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

• version bump to v2.8.9
• Merge pull request #160 from Earlopain/cgi-ruby-3.5
• Only load what is required from `cgi`
• Merge pull request #159 from flavorjones/flavorjones/ci-openbsd-202505
• ci: update ruby in the openbsd jobs
• Merge pull request #157 from flavorjones/flavorjones/fix-windows-cmake-tests
• ci: windows images no longer support older cmake versions
• Merge pull request #156 from kenhys/update-ci
• Add CI for Ruby 3.4
• Merge pull request #155 from flavorjones/flavorjones-ci-logger-fix
• dev: add logger to the Gemfile
• Merge pull request #154 from flavorjones/flavorjones-ci-fix-test-examples-macos-libiconv
• ci: brew install libiconv for test-examples on macos

↗️ minitest (indirect, 5.25.4 → 5.25.5) · Repo · Changelog

Release Notes

5.25.5 (from changelog)

• 4 bug fixes:

  • Bumped minimum ruby to 2.7.

  • Fixed expectation docs for must/wont_pattern_match. (jaredcwhite)

  • Reorder Minitest::Test.ancestors to allow reaching Minitest::Assertions#skipped? (Edouard-chin)

  • Update the ruby and rails compatibility tables. (bquorning)

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

Commits

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

• prepped for release
• - Bumped minimum ruby to 2.7.
• Added notice to readme about development versions
• - Update the ruby and rails compatibility tables. (bquorning)
• - Reorder Minitest::Test.ancestors to allow reaching Minitest::Assertions#skipped? (Edouard-chin)
• Added ruby 3.4 to CI
• - Fixed expectation docs for must/wont_pattern_match. (jaredcwhite)

↗️ rack (indirect, 2.2.14 → 2.2.16) · Repo · Changelog

Release Notes

2.2.15 (from changelog)

• Optional support for CGI::Cookie if not available. (#2327, #2333, @earlopain)

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

Commits

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

• Bump patch version.
• Change CGI::Cookie.new to Cookie.new (#2335)
• Bump patch version.
• Feature detect `CGI::Cookie`. (#2333)
• Replace usage of CGI::Cookie (#2329)
• [2.2] Update test suite for Ruby 3.5

↗️ rails-dom-testing (indirect, 2.2.0 → 2.3.0) · Repo · Changelog

Release Notes

2.3.0

What's Changed

• Add assert_not_dom, refute_dom, assert_not_select, refute_select & refute_dom_equal by @joshuay03 in #113
• Raise an error when given a block with a 0 element assertion by @joshuay03 in #116
• Raise an error when provided an invalid Range, or invalid :minimum and :maximum by @joshuay03 in #115
• assert_dom :text collapses whitespace by @jyeharry in #123

New Contributors

• @joshuay03 made their first contribution in #113
• @m-nakamura145 made their first contribution in #118
• @jyeharry made their first contribution in #122

Full Changelog: v2.2.0...v2.3.0

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

Commits

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

• Prepare for 2.3.0
• No need for CHANGELOG file. Use GitHub Releases instead
• Add release workflow
• Merge pull request #123 from jyeharry/feature/assert_dom-ignore-whitespace-v2
• Collapse whitespace from :text but not :html
• Add failing test for assert_dom collapsing whitespace
• Merge pull request #122 from jyeharry/feature/assert_dom-ignore-whitespace
• Add strict parameter to assert_dom
• Add failing test for assert_dom collapsing whitespace
• Add macos to supported platforms in Gemfile.lock
• ci: run tests once a week on a timer
• Merge pull request #124 from rails/flavorjones-dep-logger-fix
• ci: drop jruby where unsupported, pin concurrent-ruby where needed
• ci: insert Rails 7.2 and 8.0 into the testing matrix
• dep: bundle update
• Merge pull request #118 from m-nakamura145/update-checkout-action
• Update checkout action version
• doc: introduce a CHANGELOG.md file
• Merge pull request #117 from rails/flavorjones-ci-20240113
• ci: add mutex_m to the rails 7.0 gemfile
• dep: bundle update
• Merge pull request #115 from joshuay03/raise-an-error-for-invalid-ranges
• Merge pull request #116 from joshuay03/raise-an-error-for-no-elements-with-block
• Raise an error when given a block with a 0 element assertion
• Raise an error when provided an invalid Range, or invalid :minimum and :maximum
• Merge pull request #113 from joshuay03/feature/refute-and-assert-not-for-dom-and-dom-equal
• Merge pull request #114 from flavorjones/flavorjones-update-ci-matrix-2024-01
• Add `assert_not_dom`, `refute_dom`, `assert_not_select`, `refute_select` & `refute_dom_equal`
• ci: update ci matrix with rails 7.1 and ruby 3.3

↗️ zeitwerk (indirect, 2.7.1 → 2.7.3) · Repo · Changelog

Release Notes

2.7.3 (from changelog)

• The helper Zeitwerk::Loader#cpath_expected_at did not work correctly if the inflector had logic that relied on the absolute path of the given file or directory. This has been fixed.

  This bug was found by Codex.

• Perpetual internal work.

2.7.2 (from changelog)

• Internal improvements and micro-optimizations.

• Add stable TruffleRuby to CI.

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

Commits

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

• Ready for 2.7.3
• cpath_expected_at: pass correct dir to the inflector
• User Symbol#name here
• Refactor thread-safety test
• Simplify Zeitwerk::Cref#path
• Parameterize Zeitwerk::Cref::Map
• New signature convention for exceptions
• Revises duck-typing signatures
• Use #: for RBS annotations
• Updates some signature annotations
• Defines a dedicated registry for loaders
• Defines a dedicated registry for autoloads
• Refactors the registry for inceptions
• Refactors the registry for explicit namespaces
• Small simplification
• Revamp docs of Zeitwerk::Cref::Map
• Ready for 2.7.2
• Let get_or_set evaluate the fallback lazily
• Add a couple more of tests
• Define get_or_set for cref maps
• Revises some signatures
• Fixes signature annotation
• Adds a test for cref maps
• Docs improvements
• Adds code comments
• Introduce Zeitwerk::Cref::Map
• Synchronize the inceptions registry if not in CRuby
• Remove top-level constant
• Mark the private callback for namespaces as internal
• Move inceptions to their own registry
• Remove truffleruby-head from this workflow
• Add Ruby 3.4 to CI
• Merge pull request #311 from fxn/truffleruby
• Add TruffleRuby stable to CI
• Create a proper registry for explicit namespaces
• Revises some signatures
• Define Zeitwerk::Cref#to_s
• Pass crefs to the registry
• Revert "Define Zeitwerk::Cref#{to_s,hash,eql?,==}"
• Revert "Support hashing crefs whose mod has an overridden name"
• Revert "Rename some variables"
• Rename some variables
• Support hashing crefs whose mod has an overridden name
• Define Zeitwerk::Cref#{to_s,hash,eql?,==}
• Edit a comment
• Keep an eye on TruffleRuby HEAD

---

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)