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)
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.
fix(vue): Prioritize app variable to avoid duplicate name pollution (#4437)
Work in this release contributed by @yordis, @Badisi, and @lh1me. Thank you for your contribution!
6.17.0-beta.0
This beta releases 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. We also deprecated our typescript enums and our internal API class. We've detailed how to update your sdk usage if you are using the Dsn class or any of the deprecated methods in our migration documentation.
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)
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.
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)
Bumps @sentry/node from 6.2.3 to 6.17.2.
Release notes
Sourced from
@sentry/node
's releases.... (truncated)
Changelog
Sourced from
@sentry/node
's changelog.... (truncated)
Commits
37b1213
release: 6.17.20810ac8
meta: 6.17.2 CHANGELOG entrybf05736
fix(utils): Remove dom is casting (#4451)4edac41
ref(serverless): RemoverethrowAfterCapture
use in AWS lambda wrapper (#4448)5c75be0
Merge branch 'release/6.17.1'97cf273
release: 6.17.124db9af
meta: 6.17.1 CHANGELOG entry2e32c30
feat(nextjs): Add option to usehidden-source-map
as webpackdevtool
valu...472cb0c
ref(core): Renormalize event only after stringification errors (#4425)c224f9c
fix(tracing): ignore the xhr/fetch response if its request is not being track...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)