gavin/maybe
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 28 Wiki Activity

Bump sentry-ruby from 5.17.3 to 5.18.0 #933

Merged
dependabot[bot] merged 1 commits from dependabot/bundler/sentry-ruby-5.18.0 into main 2024-07-01 23:19:21 +08:00
Conversation 0 Commits 1 Files Changed 1 +3 -3
dependabot[bot] commented 2024-07-01 15:59:52 +08:00 (Migrated from github.com)
Copy Link

Bumps sentry-ruby from 5.17.3 to 5.18.0.

Changelog

Sourced from sentry-ruby's changelog.

5.18.0

Features

  • Add generator for initializer generation (#2286)

    Rails users will be able to use bin/rails generate sentry to generate their config/initializers/sentry.rb file.

  • Notify users when their custom options are discarded (#2303)

  • Add a new :graphql patch to automatically enable instrumenting GraphQL spans (#2308)

    Usage:

    Sentry.init do |config|
  # ...
  config.enabled_patches += [:graphql]
end

  • Add Sentry.get_trace_propagation_meta helper for injecting meta tags into views (#2314)

  • Add query source support to sentry-rails (#2313)

    The feature is only activated in apps that use Ruby 3.2+ and Rails 7.1+. By default only queries that take longer than 100ms will have source recorded, which can be adjusted by updating the value of config.rails.db_query_source_threshold_ms.

  • Log envelope delivery message with debug instead of info (#2320)

Bug Fixes

  • Don't throw error on arbitrary arguments being passed to capture_event options #2301
  • Decrease the default number of background worker threads by half (#2305)
  • Don't mutate enabled_environments when using Sentry::TestHelper (#2317)
  • Don't use array for transaction names and sources on scope (#2324)
    • Fixes #2257
    • BREAKING This removes the internal scope.transaction_names method, please use scope.transaction_name instead

Internal

  • Add origin to spans and transactions to track integration sources for instrumentation (#2319)
Commits

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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-ruby](https://github.com/getsentry/sentry-ruby) from 5.17.3 to 5.18.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-ruby/blob/master/CHANGELOG.md">sentry-ruby's changelog</a>.</em></p> <blockquote> <h2>5.18.0</h2> <h3>Features</h3> <ul> <li> <p>Add generator for initializer generation (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2286">#2286</a>)</p> <p>Rails users will be able to use <code>bin/rails generate sentry</code> to generate their <code>config/initializers/sentry.rb</code> file.</p> </li> <li> <p>Notify users when their custom options are discarded (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2303">#2303</a>)</p> </li> <li> <p>Add a new <code>:graphql</code> patch to automatically enable instrumenting GraphQL spans (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2308">#2308</a>)</p> <p>Usage:</p> <pre lang="rb"><code>Sentry.init do |config| # ... config.enabled_patches += [:graphql] end </code></pre> </li> <li> <p>Add <code>Sentry.get_trace_propagation_meta</code> helper for injecting meta tags into views (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2314">#2314</a>)</p> </li> <li> <p>Add query source support to <code>sentry-rails</code> (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2313">#2313</a>)</p> <p>The feature is only activated in apps that use Ruby 3.2+ and Rails 7.1+. By default only queries that take longer than 100ms will have source recorded, which can be adjusted by updating the value of <code>config.rails.db_query_source_threshold_ms</code>.</p> </li> <li> <p>Log envelope delivery message with debug instead of info (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2320">#2320</a>)</p> </li> </ul> <h3>Bug Fixes</h3> <ul> <li>Don't throw error on arbitrary arguments being passed to <code>capture_event</code> options <a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2301">#2301</a> <ul> <li>Fixes <a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2299">#2299</a></li> </ul> </li> <li>Decrease the default number of background worker threads by half (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2305">#2305</a>) <ul> <li>Fixes <a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2297">#2297</a></li> </ul> </li> <li>Don't mutate <code>enabled_environments</code> when using <code>Sentry::TestHelper</code> (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2317">#2317</a>)</li> <li>Don't use array for transaction names and sources on scope (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2324">#2324</a>) <ul> <li>Fixes <a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2257">#2257</a></li> <li><strong>BREAKING</strong> This removes the internal <code>scope.transaction_names</code> method, please use <code>scope.transaction_name</code> instead</li> </ul> </li> </ul> <h3>Internal</h3> <ul> <li>Add <code>origin</code> to spans and transactions to track integration sources for instrumentation (<a href="https://redirect.github.com/getsentry/sentry-ruby/pull/2319">#2319</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-ruby/commit/369a9204d0f6df0e2caf6adc996b0d2883fed939"><code>369a920</code></a> release: 5.18.0</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/a02b2fd69168aa650334f2be9de9e2822fb9c02d"><code>a02b2fd</code></a> Changelog for 5.18.0 (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2328">#2328</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/5c50c80a3b6a85ef0d3a48ea41f9015d0925a4c1"><code>5c50c80</code></a> Don't use array for transaction names and sources on scope (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2324">#2324</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/cfc25705ffdb92818f6911cb8ebdade92003052f"><code>cfc2570</code></a> Fix CI for rack 3.1 (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2327">#2327</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/389395eae5bf003edbf2864c258ed585443ac150"><code>389395e</code></a> Log envelope delivery message with debug instead of info (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2320">#2320</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/c317a7a29f3fe8b70bfa1f66aba368bf767fa9f7"><code>c317a7a</code></a> Add span and trace origins (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2319">#2319</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/bcf88275acb5aca6c3b1c7243d04b3e604f374bd"><code>bcf8827</code></a> <code>+=</code> instead of <code>&lt;&lt;</code> (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2317">#2317</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/7b00b250968164cb4bb6ee7ac4a777dc2e868252"><code>7b00b25</code></a> Add query source support to <code>sentry-rails</code> (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2313">#2313</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/41ab3bab04fdb7d41622799f3260ecff778cfc45"><code>41ab3ba</code></a> Add get_trace_propagation_meta helper (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2314">#2314</a>)</li> <li><a href="https://github.com/getsentry/sentry-ruby/commit/186b1e41a01bc8f42771af5c34a2444b05b39e88"><code>186b1e4</code></a> Remove nio4r pin (<a href="https://redirect.github.com/getsentry/sentry-ruby/issues/2309">#2309</a>)</li> <li>Additional commits viewable in <a href="https://github.com/getsentry/sentry-ruby/compare/5.17.3...5.18.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sentry-ruby&package-manager=bundler&previous-version=5.17.3&new-version=5.18.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@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) </details>
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
📆 Planned
Not ready to be worked on yet, but planned for future
 💻 Self Hosted only
Issues pertaining to self-hosted versions of Maybe
 ⚙️ Config
ℹ️ Needs info
Further information is requested
 📱 Mobile
Bugs exclusively happening on mobile devices
 1️⃣ High Priority
High priority issues will be worked on next
 🚨 Urgent
Issues that are urgent for app functionality
 3️⃣ Low priority
Contributions accepted, but Maybe team will not be working on this in the near term
 2️⃣ Medium Priority
Community contributions accepted, Maybe team only works on if there are no high priority items open
 ⚡ Performance
Performance issues to address
 🎨 UI / UX
Issues related to UI / UX interactions and design.
 💎 Bounty
💰 Rewarded
📊 Data issue
Issues where the app functionally works, but the data is missing or inaccurate.
 🙋 Bounty claim
$1.5K
Community
This is a great issue for community members to work on
 dependencies
Pull requests that update a dependency file
 Design
Hosted only
Hosted app only
 Required self hoster data migration
Self hosters must run data migrations to resolve this issue
 ruby
Pull requests that update Ruby code
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gavin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gavin/maybe#933
Delete Branch "dependabot/bundler/sentry-ruby-5.18.0"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?