casper/advent_leaderboard
1
0
Fork 0
Code Issues 1 Pull requests 10 Projects Releases Packages 1 Wiki Activity Actions

Update sentry-ruby monorepo to v5.26.0 #294

Open
renovate wants to merge 1 commit from renovate/sentry-ruby-monorepo into main
pull from: renovate/sentry-ruby-monorepo
merge into: casper:main
Conversation 0 Commits 1 Files changed 1 +33 -26
renovate commented 2025-01-24 10:40:49 +00:00
Collaborator
Copy link

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sentry-rails (source, changelog) 5.22.1 -> 5.26.0 age adoption passing confidence
sentry-ruby (source, changelog) 5.22.1 -> 5.26.0 age adoption passing confidence

Release Notes

getsentry/sentry-ruby (sentry-rails)

v5.26.0

Compare Source

Feature

  • Support for :logger patch which enables sending logs to Sentry when enabled_logs is set to true (#​2657)

    Here's a sample config:

    Sentry.init do |config|
... your setup ...
config.enable_logs = true
config.enabled_patches = [:logger]

end


##### Bug Fixes
- Skip creating `LogEventBuffer` if logging is not enabled ([#​2652](https://github.com/getsentry/sentry-ruby/pull/2652))

v5.25.0

Compare Source

Features
  • Support for before_send_log (#​2634)
  • Default user attributes are now automatically added to logs (#​2647)
Bug Fixes
  • Structured logging consumes way less memory now (#​2643)

v5.24.0

Compare Source

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:

```ruby
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)
  • Fix breadcrumb serialization error message to be an object (#​2584)
  • 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)

v5.23.0

Compare Source

Features
  • Add correct breadcrumb levels for 4xx/5xx response codes (#​2549)
Bug Fixes
  • Fix argument serialization for ranges that consist of ActiveSupport::TimeWithZone (#​2548)
  • Prevent starting Vernier in nested transactions (#​2528)
  • Fix TypeError when Resque.inline == true (#​2564)
Internal
  • Use File.open in LineCache (#​2566)
  • Update java backtrace regexp (#​2567)
  • Stop byteslicing empty strings in breadcrumbs (#​2574)
Miscellaneous
  • Deprecate enable_tracing in favor of traces_sample_rate = 1.0 #​2535

v5.22.4

Compare Source

Bug Fixes
  • Fix handling of cron with tz in Cron::Job (#​2530)
  • Revert "[rails] support string errors in error reporter (#​2464)" (#​2533)
  • Removed unnecessary warning about missing stackprof when Vernier is configured as the profiler (#​2537)
  • Fix regression with CheckInEvent in before_send (#​2541)
Internal
  • Introduced Configuration#validate to validate configuration in Sentry.init block (#​2538)
  • Introduced Sentry.dependency_installed? to check if a 3rd party dependency is available ie Sentry.dependency_installed?(:Vernier) (#​2542)

v5.22.3

Compare Source

Bug Fixes

v5.22.2

Compare Source

Features
  • Improve the accuracy of duration calculations in cron jobs monitoring (#​2471)
  • Use attempt_threshold to skip reporting on first N attempts (#​2503)
  • Support code.namespace for Ruby 3.4+ stacktraces (#​2506)
Bug fixes
  • Default to internal_error error type for OpenTelemetry spans #​2473
  • Improve before_send and before_send_transaction's return value handling (#​2504)
  • Fix a crash when calling Sentry.get_main_hub in a trap context (#​2510)
  • Use URI::RFC2396_PARSER.escape explicitly to remove warning logs to stderr (#​2509)
Internal

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [sentry-rails](https://github.com/getsentry/sentry-ruby/tree/5.26.0/sentry-rails) ([source](https://github.com/getsentry/sentry-ruby/tree/HEAD/sentry-rails), [changelog](https://github.com/getsentry/sentry-ruby/blob/5.26.0/CHANGELOG.md)) | `5.22.1` -> `5.26.0` | [![age](https://developer.mend.io/api/mc/badges/age/rubygems/sentry-rails/5.26.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/rubygems/sentry-rails/5.26.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/rubygems/sentry-rails/5.22.1/5.26.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/rubygems/sentry-rails/5.22.1/5.26.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [sentry-ruby](https://github.com/getsentry/sentry-ruby/tree/5.26.0/sentry-ruby) ([source](https://github.com/getsentry/sentry-ruby/tree/HEAD/sentry-ruby), [changelog](https://github.com/getsentry/sentry-ruby/blob/5.26.0/CHANGELOG.md)) | `5.22.1` -> `5.26.0` | [![age](https://developer.mend.io/api/mc/badges/age/rubygems/sentry-ruby/5.26.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/rubygems/sentry-ruby/5.26.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/rubygems/sentry-ruby/5.22.1/5.26.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/rubygems/sentry-ruby/5.22.1/5.26.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>getsentry/sentry-ruby (sentry-rails)</summary> ### [`v5.26.0`](https://github.com/getsentry/sentry-ruby/releases/tag/5.26.0) [Compare Source](https://github.com/getsentry/sentry-ruby/compare/5.25.0...5.26.0) ##### Feature - Support for `:logger` patch which enables sending logs to Sentry when `enabled_logs` is set to true ([#&#8203;2657](https://github.com/getsentry/sentry-ruby/pull/2657)) Here's a sample config: ```ruby Sentry.init do |config| ``` ##### ... your setup ... ``` config.enable_logs = true config.enabled_patches = [:logger] ``` end ``` ##### Bug Fixes - Skip creating `LogEventBuffer` if logging is not enabled ([#&#8203;2652](https://github.com/getsentry/sentry-ruby/pull/2652)) ``` ### [`v5.25.0`](https://github.com/getsentry/sentry-ruby/releases/tag/5.25.0) [Compare Source](https://github.com/getsentry/sentry-ruby/compare/5.24.0...5.25.0) ##### Features - Support for `before_send_log` ([#&#8203;2634](https://github.com/getsentry/sentry-ruby/pull/2634)) - Default user attributes are now automatically added to logs ([#&#8203;2647](https://github.com/getsentry/sentry-ruby/pull/2647)) ##### Bug Fixes - Structured logging consumes way less memory now ([#&#8203;2643](https://github.com/getsentry/sentry-ruby/pull/2643)) ### [`v5.24.0`](https://github.com/getsentry/sentry-ruby/releases/tag/5.24.0) [Compare Source](https://github.com/getsentry/sentry-ruby/compare/5.23.0...5.24.0) ##### Features - Add new sidekiq config `report_only_dead_jobs` ([#&#8203;2581](https://github.com/getsentry/sentry-ruby/pull/2581)) - Add `max_nesting` of 10 to breadcrumbs data serialization ([#&#8203;2583](https://github.com/getsentry/sentry-ruby/pull/2583)) - Add sidekiq config `propagate_traces` to control trace header injection ([#&#8203;2588](https://github.com/getsentry/sentry-ruby/pull/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. ```ruby config.sidekiq.propagate_traces = false unless Rails.const_defined?('Server') ``` - Only expose `active_storage` keys on span data if `send_default_pii` is on ([#&#8203;2589](https://github.com/getsentry/sentry-ruby/pull/2589)) - Add new `Sentry.logger` for [Structured Logging](https://develop.sentry.dev/sdk/telemetry/logs/) feature ([#&#8203;2620](https://github.com/getsentry/sentry-ruby/pull/2620)). To enable structured logging you need to turn on the `enable_logs` configuration option: ```ruby 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: ```ruby 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: ```ruby 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: ```ruby ##### 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") ``` :warning: 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 ([#&#8203;2617](https://github.com/getsentry/sentry-ruby/pull/2617)) ##### Bug Fixes - Gracefully fail on malformed utf-8 breadcrumb message ([#&#8203;2582](https://github.com/getsentry/sentry-ruby/pull/2582)) - Fixes [#&#8203;2376](https://github.com/getsentry/sentry-ruby/issues/2376) - Fix breadcrumb serialization error message to be an object ([#&#8203;2584](https://github.com/getsentry/sentry-ruby/pull/2584)) - Fixes [#&#8203;2478](https://github.com/getsentry/sentry-ruby/issues/2478) - Fix compatibility issues with sidekiq-cron 2.2.0 ([#&#8203;2591](https://github.com/getsentry/sentry-ruby/pull/2591)) - Update sentry-sidekiq to work correctly with Sidekiq 8.0 and its new timestamp format ([#&#8203;2570](https://github.com/getsentry/sentry-ruby/pull/2570)) - Ensure we capture exceptions after each job retry ([#&#8203;2597](https://github.com/getsentry/sentry-ruby/pull/2597)) ##### Internal - Remove `user_segment` from DSC ([#&#8203;2586](https://github.com/getsentry/sentry-ruby/pull/2586)) - Replace `logger` with `sdk_logger` ([#&#8203;2621](https://github.com/getsentry/sentry-ruby/pull/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. ([#&#8203;2621](https://github.com/getsentry/sentry-ruby/pull/2621)) ### [`v5.23.0`](https://github.com/getsentry/sentry-ruby/releases/tag/5.23.0) [Compare Source](https://github.com/getsentry/sentry-ruby/compare/5.22.4...5.23.0) ##### Features - Add correct breadcrumb levels for 4xx/5xx response codes ([#&#8203;2549](https://github.com/getsentry/sentry-ruby/pull/2549)) ##### Bug Fixes - Fix argument serialization for ranges that consist of ActiveSupport::TimeWithZone ([#&#8203;2548](https://github.com/getsentry/sentry-ruby/pull/2548)) - Prevent starting Vernier in nested transactions ([#&#8203;2528](https://github.com/getsentry/sentry-ruby/pull/2528)) - Fix TypeError when Resque.inline == true ([#&#8203;2564](https://github.com/getsentry/sentry-ruby/pull/2564)) ##### Internal - Use `File.open` in `LineCache` ([#&#8203;2566](https://github.com/getsentry/sentry-ruby/pull/2566)) - Update java backtrace regexp ([#&#8203;2567](https://github.com/getsentry/sentry-ruby/pull/2567)) - Stop byteslicing empty strings in breadcrumbs ([#&#8203;2574](https://github.com/getsentry/sentry-ruby/pull/2574)) ##### Miscellaneous - Deprecate `enable_tracing` in favor of `traces_sample_rate = 1.0` [#&#8203;2535](https://github.com/getsentry/sentry-ruby/pull/2535) ### [`v5.22.4`](https://github.com/getsentry/sentry-ruby/releases/tag/5.22.4) [Compare Source](https://github.com/getsentry/sentry-ruby/compare/5.22.3...5.22.4) ##### Bug Fixes - Fix handling of cron with tz in Cron::Job ([#&#8203;2530](https://github.com/getsentry/sentry-ruby/pull/2530)) - Revert "\[rails] support string errors in error reporter ([#&#8203;2464](https://github.com/getsentry/sentry-ruby/issues/2464))" ([#&#8203;2533](https://github.com/getsentry/sentry-ruby/pull/2533)) - Removed unnecessary warning about missing `stackprof` when Vernier is configured as the profiler ([#&#8203;2537](https://github.com/getsentry/sentry-ruby/pull/2537)) - Fix regression with CheckInEvent in before\_send ([#&#8203;2541](https://github.com/getsentry/sentry-ruby/pull/2541)) - Fixes [#&#8203;2540](https://github.com/getsentry/sentry-ruby/issues/2540) ##### Internal - Introduced `Configuration#validate` to validate configuration in `Sentry.init` block ([#&#8203;2538](https://github.com/getsentry/sentry-ruby/pull/2538)) - Introduced `Sentry.dependency_installed?` to check if a 3rd party dependency is available ie `Sentry.dependency_installed?(:Vernier)` ([#&#8203;2542](https://github.com/getsentry/sentry-ruby/pull/2542)) ### [`v5.22.3`](https://github.com/getsentry/sentry-ruby/releases/tag/5.22.3) [Compare Source](https://github.com/getsentry/sentry-ruby/compare/5.22.2...5.22.3) ##### Bug Fixes - Accept Hash in `before_send*` callbacks again ([#&#8203;2529](https://github.com/getsentry/sentry-ruby/pull/2529)) - Fixes [#&#8203;2526](https://github.com/getsentry/sentry-ruby/issues/2526) ### [`v5.22.2`](https://github.com/getsentry/sentry-ruby/releases/tag/5.22.2) [Compare Source](https://github.com/getsentry/sentry-ruby/compare/5.22.1...5.22.2) ##### Features - Improve the accuracy of duration calculations in cron jobs monitoring ([#&#8203;2471](https://github.com/getsentry/sentry-ruby/pull/2471)) - Use attempt\_threshold to skip reporting on first N attempts ([#&#8203;2503](https://github.com/getsentry/sentry-ruby/pull/2503)) - Support `code.namespace` for Ruby 3.4+ stacktraces ([#&#8203;2506](https://github.com/getsentry/sentry-ruby/pull/2506)) ##### Bug fixes - Default to `internal_error` error type for OpenTelemetry spans [#&#8203;2473](https://github.com/getsentry/sentry-ruby/pull/2473) - Improve `before_send` and `before_send_transaction`'s return value handling ([#&#8203;2504](https://github.com/getsentry/sentry-ruby/pull/2504)) - Fix a crash when calling `Sentry.get_main_hub` in a trap context ([#&#8203;2510](https://github.com/getsentry/sentry-ruby/pull/2510)) - Use `URI::RFC2396_PARSER.escape` explicitly to remove warning logs to stderr ([#&#8203;2509](https://github.com/getsentry/sentry-ruby/pull/2509)) ##### Internal - Test Ruby 3.4 in CI ([#&#8203;2506](https://github.com/getsentry/sentry-ruby/pull/2506)) - Upgrade actions workflows versions ([#&#8203;2506](https://github.com/getsentry/sentry-ruby/pull/2506)) - Stop relying on fugit ([#&#8203;2519](https://github.com/getsentry/sentry-ruby/pull/2519)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMjguMCIsInVwZGF0ZWRJblZlciI6IjQxLjQzLjAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
renovate force-pushed renovate/sentry-ruby-monorepo from 15431b8621 to beb678f921 2025-01-29 11:40:49 +00:00 Compare
renovate changed title from Update sentry-ruby monorepo to v5.22.2 to Update sentry-ruby monorepo to v5.22.3 2025-01-29 11:40:52 +00:00
renovate force-pushed renovate/sentry-ruby-monorepo from beb678f921 to 0f8b27dd26 2025-02-06 12:10:55 +00:00 Compare
renovate changed title from Update sentry-ruby monorepo to v5.22.3 to Update sentry-ruby monorepo to v5.22.4 2025-02-06 12:10:58 +00:00
renovate force-pushed renovate/sentry-ruby-monorepo from 0f8b27dd26 to ca9d683485 2025-03-11 13:11:10 +00:00 Compare
renovate changed title from Update sentry-ruby monorepo to v5.22.4 to Update sentry-ruby monorepo to v5.23.0 2025-03-11 13:11:12 +00:00
renovate force-pushed renovate/sentry-ruby-monorepo from ca9d683485 to e199fa00ec 2025-05-15 11:01:08 +00:00 Compare
renovate changed title from Update sentry-ruby monorepo to v5.23.0 to Update sentry-ruby monorepo to v5.24.0 2025-05-15 11:01:12 +00:00
renovate force-pushed renovate/sentry-ruby-monorepo from e199fa00ec to 2f2a9959e3 2025-06-12 11:01:20 +00:00 Compare
renovate changed title from Update sentry-ruby monorepo to v5.24.0 to Update sentry-ruby monorepo to v5.25.0 2025-06-12 11:01:22 +00:00
renovate force-pushed renovate/sentry-ruby-monorepo from 2f2a9959e3 to 4eab08abc4 2025-06-30 13:01:19 +00:00 Compare
renovate changed title from Update sentry-ruby monorepo to v5.25.0 to Update sentry-ruby monorepo to v5.26.0 2025-06-30 13:01:22 +00:00
renovate force-pushed renovate/sentry-ruby-monorepo from 4eab08abc4 to 0663292a0a 2025-07-19 12:01:37 +00:00 Compare
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/sentry-ruby-monorepo:renovate/sentry-ruby-monorepo
git switch renovate/sentry-ruby-monorepo

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff renovate/sentry-ruby-monorepo
git switch renovate/sentry-ruby-monorepo
git rebase main
git switch main
git merge --ff-only renovate/sentry-ruby-monorepo
git switch renovate/sentry-ruby-monorepo
git rebase main
git switch main
git merge --no-ff renovate/sentry-ruby-monorepo
git switch main
git merge --squash renovate/sentry-ruby-monorepo
git switch main
git merge --ff-only renovate/sentry-ruby-monorepo
git switch main
git merge renovate/sentry-ruby-monorepo
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: casper/advent_leaderboard#294
No description provided.
Delete branch "renovate/sentry-ruby-monorepo"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?