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.

Sign up for GitHub

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

Jump to bottom

Update sentry-rails 5.20.1 → 5.21.0 (minor) #1553

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update sentry-rails 5.20.1 → 5.21.0 (minor) #1553

wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Oct 25, 2024

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ sentry-rails (5.20.1 → 5.21.0) · Repo · Changelog

Release Notes

5.21.0

Features

  • Experimental support for multi-threaded profiling using Vernier (#2372)

    You can have much better profiles if you're using multi-threaded servers like Puma now by leveraging Vernier.
    To use it, first add vernier to your Gemfile and make sure it is loaded before sentry-ruby.

    # Gemfile

    gem 'vernier'
    
gem 'sentry-ruby'

    Then, set a profiles_sample_rate and the new profiler_class configuration in your sentry initializer to use the new profiler.

    # config/initializers/sentry.rb

    Sentry.init do |config|
    
# ...
    
config.profiles_sample_rate = 1.0
    
config.profiler_class = Sentry::Vernier::Profiler
    
end

Internal

  • Profile items have bigger size limit now (#2421)
  • Consistent string freezing (#2422)

Does any of this look wrong? Please let us know.

✳️ sentry-ruby (5.20.1 → 5.21.0) · Repo · Changelog

Release Notes

5.21.0

Features

  • Experimental support for multi-threaded profiling using Vernier (#2372)

    You can have much better profiles if you're using multi-threaded servers like Puma now by leveraging Vernier.
    To use it, first add vernier to your Gemfile and make sure it is loaded before sentry-ruby.

    # Gemfile

    gem 'vernier'
    
gem 'sentry-ruby'

    Then, set a profiles_sample_rate and the new profiler_class configuration in your sentry initializer to use the new profiler.

    # config/initializers/sentry.rb

    Sentry.init do |config|
    
# ...
    
config.profiles_sample_rate = 1.0
    
config.profiler_class = Sentry::Vernier::Profiler
    
end

Internal

  • Profile items have bigger size limit now (#2421)
  • Consistent string freezing (#2422)

Does any of this look wrong? Please let us know.

↗️ loofah (indirect, 2.22.0 → 2.23.1) · Repo · Changelog

Release Notes

2.23.0

2.23.0 / 2024-10-24

Added

New Contributors

Full Changelog: v2.22.0...v2.23.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 15 commits:

↗️ rack (indirect, 3.1.7 → 3.1.8) · Repo · Changelog

Release Notes

3.1.8 (from changelog)

Fixed

  • Resolve deprecation warnings about uri DEFAULT_PARSER. (#2249, @earlopain)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 2 commits:

↗️ zeitwerk (indirect, 2.6.18 → 2.7.1) · Repo · Changelog

Release Notes

2.7.1 (from changelog)

  • Micro-optimization in a hot path.

  • Raises Zeitwerk::Error if an autoloaded constant expected to represent a namespace does not store a class or module object.

  • Adds truffleruby-head to CI, except for autoloading thread-safety (see why in oracle/truffleruby#2431).

2.7.0 (from changelog)

  • Explicit namespaces can now also be defined using constant assignments.

    While constant assignments like

    # coordinates.rb

    Coordinates = Data.define(:x, :y)

    worked for most objects, they did not for classes and modules that were also namespaces (i.e., those defined by a file and matching subdirectories). In such cases, their child constants could not be autoloaded.

    This limitation has been removed.

  • TracePoint is no longer used.

  • Requires Ruby 3.2 or later.

    Gems that work with previous versions of Zeitwerk also work with this one. If they support Ruby versions older than 3.2 they can specify a relaxed version constraint for Zeitwerk like "~> 2.6", for example.

    In client projects, Bundler takes the Ruby requirement into account when resolving dependencies, so Gemfile.lock will get one compatible with the Ruby version being used.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 31 commits:

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
depfu
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants