Skip to content
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

Release v6.20.0 #657

Merged
merged 13 commits into from
Mar 29, 2021
Merged

Release v6.20.0 #657

merged 13 commits into from
Mar 29, 2021

Conversation

imjoehaines
Copy link
Contributor

Enhancements

  • Classify ActionDispatch::Http::MimeNegotiation::InvalidType as info severity level
    | #654

Fixes

  • Include connection_id in ActiveRecord breadcrumb metadata on new versons of Rails
    | #655
  • Avoid crash when Mongo 1.12 or earlier is used
    | #652
    | isabanin

isabanin and others added 13 commits March 17, 2021 10:30
Trying to use bugsnag gem together with mongo gem 1.12 raises the following error on boot: uninitialized constant Mongo::Monitoring (NameError).
…tiation-invalidtype-as-info-severity

Classify `ActionDispatch::Http::MimeNegotiation::InvalidType` errors as `info`-level severity
Bugsnag gem crashes when used with an older mongo gem (1.12)
This was inadvertently stopping us from testing on the latest v5/v6
versions as we were locked to 5.0.x/6.0.x
Rails 5.2 removed this method - we don't need it for anything so can
remove the call without further changes
…umbs

Include the connection ID in ActiveRecord breadcrumbs on new version of Rails
Loosen rails version constraint in v5 & v6 fixtures
@imjoehaines imjoehaines merged commit 98b73dc into master Mar 29, 2021
@imjoehaines imjoehaines deleted the release/v6.20.0 branch March 29, 2021 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants