search

wmcadigital / wmn-refund

Step by step form for refunds of transport tickets
https://refund.wmnetwork.co.uk
0 stars 4 forks source link

[skip netlify]: Bump @sentry/browser from 5.27.6 to 7.7.0 #622

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps @sentry/browser from 5.27.6 to 7.7.0.

Release notes

Sourced from @​sentry/browser's releases.

7.7.0

  • feat(angular): Add URL parameterization of transaction names (#5416)
  • fix(core): Add sentry_client to auth headers (#5413)
  • fix(remix): Add documentRequest function name. (#5404)
  • fix(remix): Skip capturing ok responses as errors. (#5405)
  • ref(remix): Add transaction source (#5398)

7.6.0

This release adds the source field to all outgoing transactions. See the tracking GH issue for more details.

This release also re-enables lambda layer releases for the Node Serverless SDK.

  • ref(angular): Add transaction source for Angular Router (#5382)
  • ref(build): Reenable lambda layer release in craft (#5207)
  • feat(nextjs): Record transaction name source when creating transactions (#5391)
  • ref(react): Add source to react-router-v3 (#5377)
  • ref(react): Add transaction source for react router v4/v5 (#5384)
  • ref(react): Add transaction source for react router v6 (#5385)
  • feat(remix): Wrap root with ErrorBoundary (#5365)
  • fix(remix): Move hook checks inside the wrapper component (#5371)
  • fix(remix): Strip query params from transaction names (#5368)
  • fix(remix): Make peer deps less restrictive (#5369)
  • fix(remix): Wrap handleDocumentRequest functions (#5387)
  • ref(serverless): Add transaction source (#5394)
  • feat(tracing): Add transaction source field (#5367)
  • feat(tracing): Record transaction name source when name set directly (#5396)
  • ref(tracing): Add transaction source to default router (#5386)
  • ref(tracing): Include transaction in DSC if transaction source is not an unparameterized URL (#5392)
  • feat(vue): Add transaction source to VueRouter instrumentation (#5381)

Work in this release contributed by @​moishinetzer. Thank you for your contribution!

7.5.1

This release removes the user_id and the transaction field from the dynamic sampling context data that is attached to outgoing requests as well as sent to Relay.

  • ref(tracing): Remove transaction name and user_id from DSC (#5363)

7.5.0

This release adds the sendDefaultPii flag to the Sentry.init options. When using performance monitoring capabilities of the SDK, it controls whether user IDs (set via Sentry.setUser) are propagated in the baggage header of outgoing HTTP requests. This flag is set to false per default, and acts as an opt-in mechanism for sending potentially sensitive data. If you want to attach user IDs to Sentry transactions and traces, set this flag to true but keep in mind that this is potentially sensitive information.

  • feat(sdk): Add sendDefaultPii option to the JS SDKs (#5341)
  • fix(remix): Sourcemaps upload script is missing in the tarball (#5356)
  • fix(remix): Use cjs for main entry point (#5352)
  • ref(tracing): Only add user_id to DSC if sendDefaultPii is true (#5344)

Work in this release contributed by @​jkcorrea and @​nfelger. Thank you for your contributions!

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

7.7.0

  • feat(angular): Add URL parameterization of transaction names (#5416)
  • fix(core): Add sentry_client to auth headers (#5413)
  • fix(remix): Add documentRequest function name. (#5404)
  • fix(remix): Skip capturing ok responses as errors. (#5405)
  • ref(remix): Add transaction source (#5398)

7.6.0

This release adds the source field to all outgoing transactions. See the tracking GH issue for more details.

This release also re-enables lambda layer releases for the Node Serverless SDK.

  • ref(angular): Add transaction source for Angular Router (#5382)
  • ref(build): Reenable lambda layer release in craft (#5207)
  • feat(nextjs): Record transaction name source when creating transactions (#5391)
  • ref(react): Add source to react-router-v3 (#5377)
  • ref(react): Add transaction source for react router v4/v5 (#5384)
  • ref(react): Add transaction source for react router v6 (#5385)
  • feat(remix): Wrap root with ErrorBoundary (#5365)
  • fix(remix): Move hook checks inside the wrapper component (#5371)
  • fix(remix): Strip query params from transaction names (#5368)
  • fix(remix): Make peer deps less restrictive (#5369)
  • fix(remix): Wrap handleDocumentRequest functions (#5387)
  • ref(serverless): Add transaction source (#5394)
  • feat(tracing): Add transaction source field (#5367)
  • feat(tracing): Record transaction name source when name set directly (#5396)
  • ref(tracing): Add transaction source to default router (#5386)
  • ref(tracing): Include transaction in DSC if transaction source is not an unparameterized URL (#5392)
  • feat(vue): Add transaction source to VueRouter instrumentation (#5381)

Work in this release contributed by @​moishinetzer. Thank you for your contribution!

7.5.1

This release removes the user_id and the transaction field from the dynamic sampling context data that is attached to outgoing requests as well as sent to Relay.

  • ref(tracing): Remove transaction name and user_id from DSC (#5363)

7.5.0

This release adds the sendDefaultPii flag to the Sentry.init options. When using performance monitoring capabilities of the SDK, it controls whether user IDs (set via Sentry.setUser) are propagated in the baggage header of outgoing HTTP requests. This flag is set to false per default, and acts as an opt-in mechanism for sending potentially sensitive data. If you want to attach user IDs to Sentry transactions and traces, set this flag to true but keep in mind that this is potentially sensitive information.

  • feat(sdk): Add sendDefaultPii option to the JS SDKs (#5341)
  • fix(remix): Sourcemaps upload script is missing in the tarball (#5356)

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by sentry-bot, a new releaser for @​sentry/browser since your current version.


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 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)
dependabot[bot] commented 2 years ago

Superseded by #626.