Build(deps): bump @sentry/tracing from 7.46.0 to 7.47.0 #1082

2023-04-06T04:38:16Z

argoyle commented

2023-04-06 04:38:16 +00:00

(Migrated from gitlab.com)

Bumps @sentry/tracing from 7.46.0 to 7.47.0.

Release notes

Sourced from @sentry/tracing's releases.

7.47.0

Important Changes

feat(browser): Add captureUserFeedback (#7729)

This release adds a new API, Sentry.captureUserFeedback, to browser-side SDKs that allows you to send user feedback to Sentry without loading and opening Sentry's user feedback dialog. This allows you to obtain user feedback however and whenever you want to and simply send it to Sentry using the SDK.

For instance, you can collect feedback, whenever convenient as shown in this example:
const eventId = Sentry.captureMessage('User Feedback');
const user = Sentry.getCurrentHub().getScope().getUser();
const userFeedback = {
  event_id: eventId;
  email: user.email
  name: user.username
  comments: 'I really like your App, thanks!'
}
Sentry.captureUserFeedback(userFeedback);
Note that feedback needs to be coupled to an event but as in the example above, you can just use Sentry.captureMessage to generate one.

You could also collect feedback in a custom way if an error happens and use the SDK to send it along:
Sentry.init({
  dsn: '__DSN__',
  beforeSend: event => {
    const userFeedback = collectYourUserFeedback();
    const feedback = {
      ...userFeedback,
      event_id: event.event_id.
    }
    Sentry.captureUserFeedback(feedback);
    return event;
  }
})
feat(tracing): Deprecate @sentry/tracing exports (#7611)

With this release, we officially deprecate all exports from the @sentry/tracing package, in favour of using them directly from the main SDK package. The @sentry/tracing package will be removed in a future major release.

Please take a look at the Migration docs for more details.

Additional Features and Fixes

feat(sveltekit): Add partial instrumentation for client-side fetch (#7626)

fix(angular): Handle routes with empty path (#7686)

fix(angular): Only open report dialog if error was sent (#7750)

... (truncated)

Changelog

Sourced from @sentry/tracing's changelog.

7.47.0

Important Changes

feat(browser): Add captureUserFeedback (#7729)

This release adds a new API, Sentry.captureUserFeedback, to browser-side SDKs that allows you to send user feedback to Sentry without loading and opening Sentry's user feedback dialog. This allows you to obtain user feedback however and whenever you want to and simply send it to Sentry using the SDK.

For instance, you can collect feedback, whenever convenient as shown in this example:
const eventId = Sentry.captureMessage('User Feedback');
const user = Sentry.getCurrentHub().getScope().getUser();
const userFeedback = {
  event_id: eventId;
  email: user.email
  name: user.username
  comments: 'I really like your App, thanks!'
}
Sentry.captureUserFeedback(userFeedback);
Note that feedback needs to be coupled to an event but as in the example above, you can just use Sentry.captureMessage to generate one.

You could also collect feedback in a custom way if an error happens and use the SDK to send it along:
Sentry.init({
  dsn: '__DSN__',
  beforeSend: event => {
    const userFeedback = collectYourUserFeedback();
    const feedback = {
      ...userFeedback,
      event_id: event.event_id.
    }
    Sentry.captureUserFeedback(feedback);
    return event;
  }
})
feat(tracing): Deprecate @sentry/tracing exports (#7611)

With this release, we officially deprecate all exports from the @sentry/tracing package, in favour of using them directly from the main SDK package. The @sentry/tracing package will be removed in a future major release.

Please take a look at the Migration docs for more details.

Additional Features and Fixes

feat(sveltekit): Add partial instrumentation for client-side fetch (#7626)

fix(angular): Handle routes with empty path (#7686)

... (truncated)

Commits

ad7b876 release: 7.47.0
f4861f8 Merge pull request #7758 from getsentry/prepare-release/7.47.0
56268f9 meta: Update changelog for 7.47.0
41ba98a fix(node): Disable LocalVariables integration on Node < v18 (#7748)
1d7f18f fix(replay): Ensure circular references are handled (#7752)
c90a60f feat(browser): Add captureUserFeedback (#7729)
367f779 fix(react): Only show report dialog if event was sent to Sentry (#7754)
2531853 fix(angular): Only open report dialog if error was sent (#7750)
105dcf1 feat(sveltekit): Add partial instrumentation for client-side fetch (#7626)
8ccb82d fix(node): Redact URL authority only in breadcrumbs and spans (#7740)
Additional commits viewable in compare view

Dependabot commands

You can trigger Dependabot actions by commenting on this MR

$dependabot rebase will rebase this MR
$dependabot recreate will recreate this MR rewriting all the manual changes and resolving conflicts

Bumps [@sentry/tracing](https://github.com/getsentry/sentry-javascript) from 7.46.0 to 7.47.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-javascript/releases"><code>@sentry/tracing</code>'s releases</a>.</em></p> <blockquote> <h2>7.47.0</h2> <h3>Important Changes</h3> <ul> <li><strong>feat(browser)</strong>: Add captureUserFeedback (<a href="https://github.com/getsentry/sentry-javascript/issues/7729">#7729</a>)</li> </ul> <p>This release adds a new API, <code>Sentry.captureUserFeedback</code>, to browser-side SDKs that allows you to send user feedback to Sentry without loading and opening Sentry's user feedback dialog. This allows you to obtain user feedback however and whenever you want to and simply send it to Sentry using the SDK.</p> <p>For instance, you can collect feedback, whenever convenient as shown in this example:</p> <pre lang="js"><code>const eventId = Sentry.captureMessage('User Feedback'); const user = Sentry.getCurrentHub().getScope().getUser(); const userFeedback = { event_id: eventId; email: user.email name: user.username comments: 'I really like your App, thanks!' } Sentry.captureUserFeedback(userFeedback); </code></pre> <p>Note that feedback needs to be coupled to an event but as in the example above, you can just use <code>Sentry.captureMessage</code> to generate one.</p> <p>You could also collect feedback in a custom way if an error happens and use the SDK to send it along:</p> <pre lang="js"><code>Sentry.init({ dsn: '__DSN__', beforeSend: event => { const userFeedback = collectYourUserFeedback(); const feedback = { ...userFeedback, event_id: event.event_id. } Sentry.captureUserFeedback(feedback); return event; } }) </code></pre> <ul> <li><strong>feat(tracing)</strong>: Deprecate <code>@sentry/tracing</code> exports (<a href="https://github.com/getsentry/sentry-javascript/issues/7611">#7611</a>)</li> </ul> <p>With this release, we officially deprecate all exports from the <code>@sentry/tracing</code> package, in favour of using them directly from the main SDK package. The <code>@sentry/tracing</code> package will be removed in a future major release.</p> <p>Please take a look at the <a href="https://github.com/getsentry/sentry-javascript/blob/HEAD/MIGRATION.md/#remove-requirement-for-sentrytracing-package-since-7460">Migration docs</a> for more details.</p> <h3>Additional Features and Fixes</h3> <ul> <li>feat(sveltekit): Add partial instrumentation for client-side <code>fetch</code> (<a href="https://github.com/getsentry/sentry-javascript/issues/7626">#7626</a>)</li> <li>fix(angular): Handle routes with empty path (<a href="https://github.com/getsentry/sentry-javascript/issues/7686">#7686</a>)</li> <li>fix(angular): Only open report dialog if error was sent (<a href="https://github.com/getsentry/sentry-javascript/issues/7750">#7750</a>)</li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md"><code>@sentry/tracing</code>'s changelog</a>.</em></p> <blockquote> <h2>7.47.0</h2> <h3>Important Changes</h3> <ul> <li><strong>feat(browser)</strong>: Add captureUserFeedback (<a href="https://github.com/getsentry/sentry-javascript/issues/7729">#7729</a>)</li> </ul> <p>This release adds a new API, <code>Sentry.captureUserFeedback</code>, to browser-side SDKs that allows you to send user feedback to Sentry without loading and opening Sentry's user feedback dialog. This allows you to obtain user feedback however and whenever you want to and simply send it to Sentry using the SDK.</p> <p>For instance, you can collect feedback, whenever convenient as shown in this example:</p> <pre lang="js"><code>const eventId = Sentry.captureMessage('User Feedback'); const user = Sentry.getCurrentHub().getScope().getUser(); const userFeedback = { event_id: eventId; email: user.email name: user.username comments: 'I really like your App, thanks!' } Sentry.captureUserFeedback(userFeedback); </code></pre> <p>Note that feedback needs to be coupled to an event but as in the example above, you can just use <code>Sentry.captureMessage</code> to generate one.</p> <p>You could also collect feedback in a custom way if an error happens and use the SDK to send it along:</p> <pre lang="js"><code>Sentry.init({ dsn: '__DSN__', beforeSend: event => { const userFeedback = collectYourUserFeedback(); const feedback = { ...userFeedback, event_id: event.event_id. } Sentry.captureUserFeedback(feedback); return event; } }) </code></pre> <ul> <li><strong>feat(tracing)</strong>: Deprecate <code>@sentry/tracing</code> exports (<a href="https://github.com/getsentry/sentry-javascript/issues/7611">#7611</a>)</li> </ul> <p>With this release, we officially deprecate all exports from the <code>@sentry/tracing</code> package, in favour of using them directly from the main SDK package. The <code>@sentry/tracing</code> package will be removed in a future major release.</p> <p>Please take a look at the <a href="https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md/#remove-requirement-for-sentrytracing-package-since-7460">Migration docs</a> for more details.</p> <h3>Additional Features and Fixes</h3> <ul> <li>feat(sveltekit): Add partial instrumentation for client-side <code>fetch</code> (<a href="https://github.com/getsentry/sentry-javascript/issues/7626">#7626</a>)</li> <li>fix(angular): Handle routes with empty path (<a href="https://github.com/getsentry/sentry-javascript/issues/7686">#7686</a>)</li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-javascript/commit/ad7b8766faf7c6399637df116614f53e19648e9d"><code>ad7b876</code></a> release: 7.47.0</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/f4861f8c3eab1181ab8e7544402b23770a992d6e"><code>f4861f8</code></a> Merge pull request <a href="https://github.com/getsentry/sentry-javascript/issues/7758">#7758</a> from getsentry/prepare-release/7.47.0</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/56268f9ae5414c20dda21aaeec77cca1e50a15c9"><code>56268f9</code></a> meta: Update changelog for 7.47.0</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/41ba98a53d3aa1a7eeac3629468528996d2b3002"><code>41ba98a</code></a> fix(node): Disable <code>LocalVariables</code> integration on Node < v18 (<a href="https://github.com/getsentry/sentry-javascript/issues/7748">#7748</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/1d7f18f96998c13f1cc059ca1e3fbe0c27c7b7f6"><code>1d7f18f</code></a> fix(replay): Ensure circular references are handled (<a href="https://github.com/getsentry/sentry-javascript/issues/7752">#7752</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/c90a60f44c04ff340a61fbf8f9b9ea2609605a03"><code>c90a60f</code></a> feat(browser): Add <code>captureUserFeedback</code> (<a href="https://github.com/getsentry/sentry-javascript/issues/7729">#7729</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/367f779856566840bc703aa0fb5793b4e7e67148"><code>367f779</code></a> fix(react): Only show report dialog if event was sent to Sentry (<a href="https://github.com/getsentry/sentry-javascript/issues/7754">#7754</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/2531853c0f068e6c18520d529b64a431e3a35168"><code>2531853</code></a> fix(angular): Only open report dialog if error was sent (<a href="https://github.com/getsentry/sentry-javascript/issues/7750">#7750</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/105dcf17867069dfa89ecfdf97a6b766e8326aa0"><code>105dcf1</code></a> feat(sveltekit): Add partial instrumentation for client-side fetch (<a href="https://github.com/getsentry/sentry-javascript/issues/7626">#7626</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript/commit/8ccb82d5e8cb7ab27377ca0f30c716ee01d1169d"><code>8ccb82d</code></a> fix(node): Redact URL authority only in breadcrumbs and spans (<a href="https://github.com/getsentry/sentry-javascript/issues/7740">#7740</a>)</li> <li>Additional commits viewable in <a href="https://github.com/getsentry/sentry-javascript/compare/7.46.0...7.47.0">compare view</a></li> </ul> </details> <br /> --- <details> <summary>Dependabot commands</summary> <br /> You can trigger Dependabot actions by commenting on this MR - `$dependabot rebase` will rebase this MR - `$dependabot recreate` will recreate this MR rewriting all the manual changes and resolving conflicts </details>

argoyle commented

2023-04-06 08:12:55 +00:00

(Migrated from gitlab.com)

$dependabot recreate

argoyle commented

2023-04-06 08:12:56 +00:00

(Migrated from gitlab.com)

⚠️ dependabot is recreating merge request. All changes will be overwritten! ⚠️

:warning: `dependabot` is recreating merge request. All changes will be overwritten! :warning:

argoyle commented

2023-04-06 08:13:00 +00:00

(Migrated from gitlab.com)

❌ dependabot failed recreating merge request.

undefined method `package_manager' for nil:NilClass

        name_normaliser[dep] ||= Dependency.name_normaliser_for_package_manager(dep.package_manager)
                                                                                   ^^^^^^^^^^^^^^^^

:x: `dependabot` failed recreating merge request. ``` undefined method `package_manager' for nil:NilClass name_normaliser[dep] ||= Dependency.name_normaliser_for_package_manager(dep.package_manager) ^^^^^^^^^^^^^^^^ ```

argoyle (Migrated from gitlab.com) closed this pull request

2023-04-06 08:13:11 +00:00

argoyle commented

2023-04-06 08:13:13 +00:00

(Migrated from gitlab.com)

Dependabot won't notify anymore about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

Dependabot won't notify anymore about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file.

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dancefinder/dancefinder-app#1082