sattarab / noblequran

0 stars 0 forks source link

Bump @sentry/node from 6.2.3 to 6.17.5 in /server #658

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps @sentry/node from 6.2.3 to 6.17.5.

Release notes

Sourced from @​sentry/node's releases.

6.17.5

This release deprecates the Severity enum, the SeverityLevel type, and the internal SeverityLevels array, all from @sentry/types. In v7, Severity will disappear (in favor of SeverityLevel) and SeverityLevel and SeverityLevels will live in @sentry/utils. If you are using any of the three, we encourage you to migrate your usage now, using our migration guide.

  • ref: Export Session class from core/browser/node (#4508)
  • chore(nextjs): Bump@sentry/webpack-plugin to 1.18.5 (#4501)
  • ref(types): Move SeverityLevel and SeverityLevels to @sentry/utils (#4492)
  • fix(vue): Cast name parameter to string (#4483)

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

6.17.4

  • chore(deps): Bump @sentry/webpack-plugin from 1.18.3 to 1.18.4 (#4464)
  • fix(browser): Set severity level for events captured by the global error handler (#4460)
  • fix(integrations): Add default for ExtraErrorData's depth option (#4487)
  • fix(nextjs): Export BrowserTracing integration directly (#4480)
  • fix(tracing): Export SpanStatus enum (#4478)
  • fix(vue): Property _isVue not defined in Vue3 (#4461)

Work in this release contributed by @​7inspire, @​jaeseokk, and @​rchl. Thank you for your contributions!

6.17.3

  • fix(nextjs): Unwrap req and res if necessary when instrumenting server (#4467)

6.17.2

This patch contains a breaking change for anyone setting the undocumented rethrowAfterCapture option for @sentry/serverless's AWS wrapper to false, as its functionality has been removed. For backwards compatibility with anyone setting it to true (which is also the default), the option remains in the WrapperOptions type for now. It will be removed in the next major release, though, so we recommend removing it from your code.

  • ref(serverless): Remove rethrowAfterCapture use in AWS lambda wrapper (#4448)
  • fix(utils): Remove dom is casting (#4451)

6.17.1

  • ref(core): Renormalize event only after stringification errors (#4425)
  • feat(nextjs): Add option to use hidden-source-map as webpack devtool value (#4436)
  • fix(tracing): ignore the xhr/fetch response if its request is not being tracked (#4428)
  • fix(vue): prevent after hook from starting new span (#4438)

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

6.17.0

This release contains several internal refactors that help reduce the bundle size of the SDK and help prep for our upcoming major release. There are no breaking changes in this patch unless you are using our internal Dsn class, which has been removed. We also deprecated a few of our typescript enums and our internal API class. We've detailed in our migration documentation how to update your sdk usage if you are using any of these in your code.

  • feat: Remove Dsn class (#4325)
  • feat(core): Add processing metadata to scope and event (#4252)
  • feat(core): Deprecate API class (#4281)
  • feat(ember): Update ember dependencies (#4253)
  • fix(nextjs): Inject sentry.x.config.js into pages/_error (#4397)
  • fix(nextjs): Add sentry-cli existence check for enabling webpack plugin #4311
  • ref(tracing): deprecate span status enum (#4299)
  • ref(tracing): Remove script evaluation span (#4433)
  • ref(types): drop unused logLevel (#4317)
  • ref(types): deprecate request status enum (#4316)

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

6.17.5

This release deprecates the Severity enum, the SeverityLevel type, and the internal SeverityLevels array, all from @sentry/types. In v7, Severity will disappear (in favor of SeverityLevel) and SeverityLevel and SeverityLevels will live in @sentry/utils. If you are using any of the three, we encourage you to migrate your usage now, using our migration guide.

  • ref: Export Session class from core/browser/node (#4508)
  • chore(nextjs): Bump@sentry/webpack-plugin to 1.18.5 (#4501)
  • ref(types): Move SeverityLevel and SeverityLevels to @sentry/utils (#4492)
  • fix(vue): Cast name parameter to string (#4483)

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

6.17.4

  • chore(deps): Bump @sentry/webpack-plugin from 1.18.3 to 1.18.4 (#4464)
  • fix(browser): Set severity level for events captured by the global error handler (#4460)
  • fix(integrations): Add default for ExtraErrorData's depth option (#4487)
  • fix(nextjs): Export BrowserTracing integration directly (#4480)
  • fix(tracing): Export SpanStatus enum (#4478)
  • fix(vue): Property _isVue not defined in Vue3 (#4461)

Work in this release contributed by @​7inspire, @​jaeseokk, and @​rchl. Thank you for your contributions!

6.17.3

  • fix(nextjs): Unwrap req and res if necessary when instrumenting server (#4467)

6.17.2

This patch contains a breaking change for anyone setting the undocumented rethrowAfterCapture option for @sentry/serverless's AWS wrapper to false, as its functionality has been removed. For backwards compatibility with anyone setting it to true (which is also the default), the option remains in the WrapperOptions type for now. It will be removed in the next major release, though, so we recommend removing it from your code.

  • ref(serverless): Remove rethrowAfterCapture use in AWS lambda wrapper (#4448)
  • fix(utils): Remove dom is casting (#4451)

6.17.1

  • ref(core): Renormalize event only after stringification errors (#4425)
  • feat(nextjs): Add option to use hidden-source-map as webpack devtool value (#4436)
  • fix(tracing): ignore the xhr/fetch response if its request is not being tracked (#4428)
  • fix(vue): prevent after hook from starting new span (#4438)

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

6.17.0

This release contains several internal refactors that help reduce the bundle size of the SDK and help prep for our upcoming major release. There are no breaking changes in this patch unless you are using our internal Dsn class, which has been removed. We also deprecated a few of our typescript enums and our internal API class. We've detailed in our migration documentation how to update your sdk usage if you are using any of these in your code.

  • feat: Remove Dsn class (#4325)
  • feat(core): Add processing metadata to scope and event (#4252)
  • feat(core): Deprecate API class (#4281)
  • feat(ember): Update ember dependencies (#4253)

... (truncated)

Commits
  • 82779c3 release: 6.17.5
  • 1b76fff meta: 6.17.5 CHANGELOG entry (#4510)
  • 11cd0e1 chore(nextjs): Bump@sentry/webpack-plugin to 1.18.5 (#4501)
  • 6fbec97 ref: Export Session class from core/browser/node (#4508)
  • d898730 ref(integrations): Simplify calling original method in CaptureConsole (#4505)
  • 1a6c26e chore(nextjs): Remove require call on TypeScript file (#4498)
  • ad37109 chore(docs): Properly close code section (#4496)
  • 9ca911b ref(types): Move SeverityLevel and SeverityLevels to @sentry/utils (#4492)
  • b6a6142 test(tracing): Add tests for backgroundtab. (#4443)
  • 6309dd6 fix(vue): Cast name parameter to string (#4483)
  • Additional commits viewable in compare view


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 #661.