Bump sentry-rails and sentry-ruby

[dependabot]

Bumps sentry-rails and sentry-ruby. These dependencies needed to be updated together.
Updates sentry-rails from 5.11.0 to 5.12.0

Changelog

Sourced from sentry-rails's changelog.

5.12.0

Features

• Record client reports for profiles #2107
• Adopt Rails 7.1's new BroadcastLogger #2120
• Support sending events after all retries were performed (sentry-resque) #2087
• Add Cron Monitoring support

  • Add Sentry.capture_check_in API for Cron Monitoring #2117

    You can now track progress of long running scheduled jobs.

    check_in_id = Sentry.capture_check_in('job_name', :in_progress)
    # do job stuff
    Sentry.capture_check_in('job_name', :ok, check_in_id: check_in_id)

  • Add Sentry::Cron::MonitorCheckIns module for automatic monitoring of jobs #2130

    Standard job frameworks such as ActiveJob and Sidekiq can now use this module to automatically capture check ins.

    class ExampleJob < ApplicationJob
      include Sentry::Cron::MonitorCheckIns
    sentry_monitor_check_ins
    def perform(*args)
    # do stuff
    end
    end

    class SidekiqJob
      include Sidekiq::Job
      include Sentry::Cron::MonitorCheckIns
    sentry_monitor_check_ins
    def perform(*args)
    # do stuff
    end
    end

    You can pass in optional attributes to sentry_monitor_check_ins as follows.

    # slug defaults to the job class name
    sentry_monitor_check_ins slug: 'custom_slug'

... (truncated)

Commits

• e09786c release: 5.12.0
• 01c6a3b changelog for 5.12.0 (#2133)
• 71ec4f4 Add option to notify Sentry only after the last retry on resque (#2087)
• 65ef04c Add Sentry::Cron::MonitorCheckIns module for automatic monitoring of jobs (...
• 3d0ed07 Update setup for Rails 7.1 (#2125)
• 286135c Add new Sentry.capture_check_in API for Cron monitoring (#2117)
• 096e6c3 Fix CI badges (#2129)
• ba29bb8 Try codecov components and use official action for uploads (#2128)
• 58ff7f0 Add SimpleCov.command_name for isolated_specs (#2127)
• 58253af update craft config for release registry (#2121)
• Additional commits viewable in compare view

Updates sentry-ruby from 5.11.0 to 5.12.0

Changelog

Sourced from sentry-ruby's changelog.

5.12.0

Features

• Record client reports for profiles #2107
• Adopt Rails 7.1's new BroadcastLogger #2120
• Support sending events after all retries were performed (sentry-resque) #2087
• Add Cron Monitoring support

  • Add Sentry.capture_check_in API for Cron Monitoring #2117

    You can now track progress of long running scheduled jobs.

    check_in_id = Sentry.capture_check_in('job_name', :in_progress)
    # do job stuff
    Sentry.capture_check_in('job_name', :ok, check_in_id: check_in_id)

  • Add Sentry::Cron::MonitorCheckIns module for automatic monitoring of jobs #2130

    Standard job frameworks such as ActiveJob and Sidekiq can now use this module to automatically capture check ins.

    class ExampleJob < ApplicationJob
      include Sentry::Cron::MonitorCheckIns
    sentry_monitor_check_ins
    def perform(*args)
    # do stuff
    end
    end

    class SidekiqJob
      include Sidekiq::Job
      include Sentry::Cron::MonitorCheckIns
    sentry_monitor_check_ins
    def perform(*args)
    # do stuff
    end
    end

    You can pass in optional attributes to sentry_monitor_check_ins as follows.

    # slug defaults to the job class name
    sentry_monitor_check_ins slug: 'custom_slug'

... (truncated)

Commits

• e09786c release: 5.12.0
• 01c6a3b changelog for 5.12.0 (#2133)
• 71ec4f4 Add option to notify Sentry only after the last retry on resque (#2087)
• 65ef04c Add Sentry::Cron::MonitorCheckIns module for automatic monitoring of jobs (...
• 3d0ed07 Update setup for Rails 7.1 (#2125)
• 286135c Add new Sentry.capture_check_in API for Cron monitoring (#2117)
• 096e6c3 Fix CI badges (#2129)
• ba29bb8 Try codecov components and use official action for uploads (#2128)
• 58ff7f0 Add SimpleCov.command_name for isolated_specs (#2127)
• 58253af update craft config for release registry (#2121)
• Additional commits viewable 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)