Skip to content

Commit

Permalink
Upgrade: Bump sentry-ruby from 5.19.0 to 5.22.1
Browse files Browse the repository at this point in the history
Bumps [sentry-ruby](https://github.com/getsentry/sentry-ruby) from 5.19.0 to 5.22.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.19.0...5.22.1)

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

Signed-off-by: dependabot[bot] <[email protected]>
  • Loading branch information
dependabot[bot] authored Dec 23, 2024
1 parent ae8aed0 commit e3a0fd6
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 7 deletions.
2 changes: 1 addition & 1 deletion Gemfile
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ gem 'ruby-progressbar', '~> 1.13'
gem 'scenic', '~> 1.8'
gem 'seed-fu', '~> 2.3'
gem 'sentry-rails', '~> 5.19'
gem 'sentry-ruby', '~> 5.17'
gem 'sentry-ruby', '~> 5.22'
gem 'sentry-sidekiq', '~> 5.19'
gem 'sidekiq', '~> 7.3'
gem 'sidekiq-cron', '~> 1.12'
Expand Down
12 changes: 6 additions & 6 deletions Gemfile.lock
Original file line number Diff line number Diff line change
Expand Up @@ -514,14 +514,14 @@ GEM
seed-fu (2.3.9)
activerecord (>= 3.1)
activesupport (>= 3.1)
sentry-rails (5.19.0)
sentry-rails (5.22.1)
railties (>= 5.0)
sentry-ruby (~> 5.19.0)
sentry-ruby (5.19.0)
sentry-ruby (~> 5.22.1)
sentry-ruby (5.22.1)
bigdecimal
concurrent-ruby (~> 1.0, >= 1.0.2)
sentry-sidekiq (5.19.0)
sentry-ruby (~> 5.19.0)
sentry-sidekiq (5.22.1)
sentry-ruby (~> 5.22.1)
sidekiq (>= 3.0)
shoulda-matchers (6.3.0)
activesupport (>= 5.2.0)
Expand Down Expand Up @@ -650,7 +650,7 @@ DEPENDENCIES
scenic (~> 1.8)
seed-fu (~> 2.3)
sentry-rails (~> 5.19)
sentry-ruby (~> 5.17)
sentry-ruby (~> 5.22)
sentry-sidekiq (~> 5.19)
shoulda-matchers (~> 6.1)
sidekiq (~> 7.3)
Expand Down

0 comments on commit e3a0fd6

Please sign in to comment.