Skip to content

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Oct 4, 2022

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.4.2 → 5.5.0) · Repo · Changelog

Release Notes

5.5.0

Features

  • Support rack 3 #1884

    • We no longer need the HTTP_VERSION check for ignoring the header
  • Add Dynamic Sampling support
    The SDK now supports Sentry's Dynamic Sampling product.

    Note that this is not supported for users still using the config.async option.

    • Parse incoming W3C Baggage Headers and propagate them to continue traces #1869
    • Create new Baggage entries as Head SDK (originator of trace) #1898
    • Add Transaction source annotations to classify low quality (high cardinality) transaction names #1902

Bug Fixes

  • Memoize session.aggregation_key #1892
  • Execute with_scope's block even when SDK is not initialized #1897
  • Make sure test helper clears the current scope before/after a test #1900

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

✳️ sentry-ruby (5.4.2 → 5.5.0) · Repo · Changelog

Release Notes

5.5.0

Features

  • Support rack 3 #1884

    • We no longer need the HTTP_VERSION check for ignoring the header
  • Add Dynamic Sampling support
    The SDK now supports Sentry's Dynamic Sampling product.

    Note that this is not supported for users still using the config.async option.

    • Parse incoming W3C Baggage Headers and propagate them to continue traces #1869
    • Create new Baggage entries as Head SDK (originator of trace) #1898
    • Add Transaction source annotations to classify low quality (high cardinality) transaction names #1902

Bug Fixes

  • Memoize session.aggregation_key #1892
  • Execute with_scope's block even when SDK is not initialized #1897
  • Make sure test helper clears the current scope before/after a test #1900

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

↗️ zeitwerk (indirect, 2.6.0 → 2.6.1) · Repo · Changelog

Release Notes

2.6.1 (from changelog)

  • Zeitwerk::Loader#dirs allows you to instrospect the root directories configured in the receiver. Please check its documentation for details.

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

Commits

See the full diff on Github. The new version differs by 14 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 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 4, 2022
@mitlib mitlib temporarily deployed to mit-bento-pr-1085 October 4, 2022 16:21 Inactive
@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.197% when pulling 173c2f9 on depfu/update/group/sentry-ruby-core-5.5.0 into c51d6c0 on main.

@depfu
Copy link
Contributor Author

depfu bot commented Oct 21, 2022

Closing because this update has already been applied

@depfu depfu bot closed this Oct 21, 2022
@depfu depfu bot deleted the depfu/update/group/sentry-ruby-core-5.5.0 branch October 21, 2022 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants