Skip to content

Bump sentry-raven from 3.0.4 to 3.1.0 #549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 19, 2020

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 18, 2020

Bumps sentry-raven from 3.0.4 to 3.1.0.

Release notes

Sourced from sentry-raven's releases.

3.1.0

Feature

  • Exclude all 4xx Rails errors (#1004)

    See the full list here

  • Add some error context in transport_failure_callback (#1003)

    Before:

    config.transport_failure_callback = lambda { |event|
      AdminMailer.email_admins("Oh god, it's on fire!", event).deliver_later
    }

    After:

    config.transport_failure_callback = lambda { |event, error|
      AdminMailer.email_admins("Oh god, it's on fire because #{error.message}!", event).deliver_later
    }
  • Support cleaning up exception backtrace with customized backtrace_cleaner (#1011)

    The new config backtrace_cleanup_callback takes a lambda/proc object (default is nil) and will be called with exception's backtrace

    Raven.configure do |config|
      config.backtrace_cleanup_callback = lambda do |backtrace|
        Rails.backtrace_cleaner.clean(backtrace)
      end
    end

    And with the Rails integration, it'll automatically use a customized Raven::Rails::BacktraceCleaner to clean up exception's backtrace. It's basically Rails 6's backtrace cleaner but without silencers.

    The main reason to add this cleaner is to remove template methods from the trace, e.g.

    app/views/welcome/view_error.html.erb in _app_views_welcome_view_error_html_erb__2807287320172182514_65600 at line 1
    

    will become

    app/views/welcome/view_error.html.erb at line 1
    
Changelog

Sourced from sentry-raven's changelog.

3.1.0

Feature

  • Exclude all 4xx Rails errors (#1004)

    See the full list here

  • Add some error context in transport_failure_callback (#1003)

    Before:

    config.transport_failure_callback = lambda { |event|
      AdminMailer.email_admins("Oh god, it's on fire!", event).deliver_later
    }

    After:

    config.transport_failure_callback = lambda { |event, error|
      AdminMailer.email_admins("Oh god, it's on fire because #{error.message}!", event).deliver_later
    }
  • Support cleaning up exception backtrace with customized backtrace_cleaner (#1011)

    The new config backtrace_cleanup_callback takes a lambda/proc object (default is nil) and will be called with exception's backtrace

    Raven.configure do |config|
      config.backtrace_cleanup_callback = lambda do |backtrace|
        Rails.backtrace_cleaner.clean(backtrace)
      end
    end

    And with the Rails integration, it'll automatically use a customized Raven::Rails::BacktraceCleaner to clean up exception's backtrace. It's basically Rails 6's backtrace cleaner but without silencers.

    The main reason to add this cleaner is to remove template methods from the trace, e.g.

    app/views/welcome/view_error.html.erb in _app_views_welcome_view_error_html_erb__2807287320172182514_65600 at line 1
    

    will become

    app/views/welcome/view_error.html.erb at line 1
    
Commits
  • dfe16f1 release: 3.1.0
  • 49e97d2 Fix changelog's format
  • 0cb173d Revert "Update changelog for version 3.1.0"
  • 1f75f5c Revert "Remove Unreleased header"
  • 78cc6e7 Remove Unreleased header
  • a41c765 Update changelog for version 3.1.0
  • 2b71009 Update CHANGELOG.md (#1028)
  • f43c36c Update CHANGELOG.md
  • 0ab5a47 Return value of rescue_with_handler when intercepting ActiveJob exceptions ...
  • a5f101a Revert rack-timeout deprecation (#1026)
  • Additional commits viewable in compare view

Dependabot compatibility score

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

@dependabot dependabot bot added dependencies Pull requests that update a dependency file ruby Pull requests that update Ruby code labels Sep 18, 2020
@colby-swandale colby-swandale merged commit 2187e66 into master Sep 19, 2020
@colby-swandale colby-swandale deleted the dependabot/bundler/sentry-raven-3.1.0 branch September 19, 2020 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file ruby Pull requests that update Ruby code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant