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

Bump sentry-sidekiq from 5.3.1 to 5.4.1 #11400

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 7, 2022

Bumps sentry-sidekiq from 5.3.1 to 5.4.1.

Changelog

Sourced from sentry-sidekiq's changelog.

5.4.1

Bug Fixes

  • Fix missing spec.files in sentry-ruby.gemspec

5.4.0

Features

  • Expose :values in ExceptionInterface, so that it can be accessed in before_send under event.exception.values #1843

  • Add top level Sentry.close API #1844

    • Cleans up SDK state and sets it to uninitialized
    • No-ops all SDK APIs and also disables the transport layer, so nothing will be sent to Sentry after closing the SDK
  • Handle exception with large stacktrace without dropping entire item #1807

  • Capture Rails runner's exceptions before exiting #1820

  • Add Sentry.with_exception_captured helper #1814

    Usage:

    Sentry.with_exception_captured do
     1/1 #=> 1 will be returned
    end
    Sentry.with_exception_captured do
    1/0 #=> ZeroDivisionError will be reported and re-raised
    end

  • Prepare for Rails 7.1's error reporter API change #1834

  • Set sentry.error_event_id in request env if the middleware captures errors #1849

    If the SDK's Rack middleware captures an error, the reported event's id will be stored in the request env. For example:

    env["sentry.error_event_id"] #=> "507bd4c1a07e4355bb70bcd7afe8ab17"

    Users can display this information on the error page via a middleware as proposed in #1846

Bug Fixes

  • Respect report_rescued_exceptions config #1847
  • Rescue event's to JSON conversion error #1853
  • Rescue ThreadError in SessionFlusher and stop creating threads if flusher is killed #1851

... (truncated)

Commits
  • 460dd6d release: 5.4.1
  • 09308ab Fix missing spec.files in sentry-ruby.gemspec (#1857)
  • 7ff81bf Merge branch 'release/5.4.0'
  • abbc62f release: 5.4.0
  • 3e854ac Prepare CHANGELOG for 5.4.0 release
  • b30722e Add exited status to SessionFlusher and rescue ThreadError (#1851)
  • 3323159 Bump terser from 4.8.0 to 4.8.1 in /sentry-rails/examples/rails-6.0 (#1852)
  • 6118b66 Bump terser from 4.8.0 to 4.8.1 in /sentry-raven/examples/rails-6.0 (#1850)
  • 3326fe0 Revert "CHANGELOG"
  • d9265c3 CHANGELOG
  • 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)

Bumps [sentry-sidekiq](https://github.com/getsentry/sentry-ruby) from 5.3.1 to 5.4.1.
- [Release notes](https://github.com/getsentry/sentry-ruby/releases)
- [Changelog](https://github.com/getsentry/sentry-ruby/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-ruby@5.3.1...5.4.1)

---
updated-dependencies:
- dependency-name: sentry-sidekiq
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file Ruby labels Sep 7, 2022
@gitpod-io
Copy link

gitpod-io bot commented Sep 7, 2022

@codeclimate
Copy link

codeclimate bot commented Sep 7, 2022

Code Climate has analyzed commit 2bc7fdc and detected 0 issues on this pull request.

View more on Code Climate.

@github-actions
Copy link

github-actions bot commented Sep 7, 2022

This pull request generated screenshots of many common pages in the running app. You should be able to download and view them here:
https://github.com/publiclab/plots2/suites/8178320146/artifacts/355605616

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Sep 12, 2022

Superseded by #11404.

@dependabot dependabot bot closed this Sep 12, 2022
@dependabot dependabot bot deleted the dependabot/bundler/sentry-sidekiq-5.4.1 branch September 12, 2022 09:44
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants