Bump sentry-raven from 3.0.4 to 3.1.0 (!1770) · Merge requests · thoughtbot, inc. / administrate

Merged Administrator requested to merge dependabot/bundler/sentry-raven-3.1.0 into master Sep 18, 2020

Created by: dependabot-preview[bot]

Bumps sentry-raven from 3.0.4 to 3.1.0.

Release notes

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 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 use these labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
@dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

Update frequency (including time of day and day of week)
Pull request limits (per update run and/or open at any time)
Automerge options (never/patch/minor, and dev/runtime dependencies)
Out-of-range updates (receive only lockfile updates, if desired)
Security updates (receive only security updates, if desired)