Bump sentry-sidekiq from 5.23.0 to 5.24.0 #2265

2025-05-19T15:45:47+08:00

dependabot[bot] commented

2025-05-19 15:45:47 +08:00

(Migrated from github.com)

Bumps sentry-sidekiq from 5.23.0 to 5.24.0.

Changelog

Sourced from sentry-sidekiq's changelog.

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")

... (truncated)

Commits

cad4b3f release: 5.24.0
63b5162 Replace logger with sdk_logger (#2621)
407ea0b Fix flaky spec (#2614)
7265f14 Sidekiq 8.0 updates (#2570)
5e8db8d Fix jruby on CI (#2609)
6b15516 Add sidekiq config propagate_traces to control trace header injection (#2588)
a884cae Fix compatibility issues with sidekiq-cron 2.2.0 (#2591)
bfa8b49 Add new sidekiq config (#2581)
0043161 [sidekiq] add basic Vernier spec (#2465)
ec75893 [sidekiq] Add sidekiq from main for testing (#2578)
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [sentry-sidekiq](https://github.com/getsentry/sentry-ruby) from 5.23.0 to 5.24.0. <details> <summary>Changelog</summary> Sourced from <a href="https://github.com/getsentry/sentry-ruby/blob/master/CHANGELOG.md">sentry-sidekiq's changelog</a>. <blockquote> <h2>5.24.0</h2> <h3>Features</h3> <ul> <li> Add new sidekiq config <code>report_only_dead_jobs</code> (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2581">#2581</a>) </li> <li> Add <code>max_nesting</code> of 10 to breadcrumbs data serialization (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2583">#2583</a>) </li> <li> Add sidekiq config <code>propagate_traces</code> to control trace header injection (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2588">#2588</a>) 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. <pre lang="ruby"><code>config.sidekiq.propagate_traces = false unless Rails.const_defined?('Server') </code></pre> </li> <li> Only expose <code>active_storage</code> keys on span data if <code>send_default_pii</code> is on (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2589">#2589</a>) </li> <li> Add new <code>Sentry.logger</code> for <a href="https://develop.sentry.dev/sdk/telemetry/logs/">Structured Logging</a> feature (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2620">#2620</a>). To enable structured logging you need to turn on the <code>enable_logs</code> configuration option: <pre lang="ruby"><code>Sentry.init do |config| # ... your setup ... config.enable_logs = true end </code></pre> Once you configured structured logging, you get access to a new <code>Sentry.logger</code> object that can be used as a regular logger with additional structured data support: <pre lang="ruby"><code>Sentry.logger.info("User logged in", user_id: 123) Sentry.logger.error("Failed to process payment", transaction_id: "tx_123", error_code: "PAYMENT_FAILED" ) </code></pre> You can also use message templates with positional or hash parameters: <pre lang="ruby"><code>Sentry.logger.info("User %{name} logged in", name: "Jane Doe") Sentry.logger.info("User %s logged in", ["Jane Doe"]) </code></pre> Any other arbitrary attributes will be sent as part of the log event payload: <pre lang="ruby"><code># 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") </code></pre> </li> </ul>  </blockquote> ... (truncated) </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-ruby/commit/cad4b3fe4ec8726dd371fb0894e5cf5829b3852d"><code>cad4b3f</code></a> release: 5.24.0</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/63b5162309e449b009ce153fd1ce2e059a216e1b"><code>63b5162</code></a> Replace logger with sdk_logger (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2621">#2621</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/407ea0bcd12ae25a9cb0f9409093445ea9b7dcf6"><code>407ea0b</code></a> Fix flaky spec (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2614">#2614</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/7265f144ed25e1a7ef60762ad7f934c319a745cf"><code>7265f14</code></a> Sidekiq 8.0 updates (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2570">#2570</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/5e8db8d853dd20cd5e055691145224c8c1972375"><code>5e8db8d</code></a> Fix jruby on CI (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2609">#2609</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/6b155167f367f08b5a4333fa4b21c48a11b74e5b"><code>6b15516</code></a> Add sidekiq config propagate_traces to control trace header injection (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2588">#2588</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/a884caee95ddf3c29cec4761ab423ed56e0b16b5"><code>a884cae</code></a> Fix compatibility issues with <code>sidekiq-cron</code> <code>2.2.0</code> (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2591">#2591</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/bfa8b49980cdb6c6878818fcdc606b2d59f32873"><code>bfa8b49</code></a> Add new sidekiq config (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2581">#2581</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/0043161a7d36f2b17545d211a87e6b6bce99c99c"><code>0043161</code></a> [sidekiq] add basic Vernier spec (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2465">#2465</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/ec75893d78f28bba3d6831326471733b3499653e"><code>ec75893</code></a> [sidekiq] Add sidekiq from main for testing (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2578">#2578</a>)</li> <li>See full diff in <a href="https://github.com/getsentry/sentry-ruby/compare/5.23.0...5.24.0">compare view</a></li> </ul> </details> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sentry-sidekiq&package-manager=bundler&previous-version=5.23.0&new-version=5.24.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: gavin/maybe#2265