docs/changelog/v6.md
Sentry SDK v6 is no longer supported. We recommend migrating to the latest version of the SDK. You can start by
migrating from v6 of the SDK to v7 by following the migration guide.
Work in this release contributed by @cameronaziz and @kpdecker. Thank you for your contributions!
build/types to tarballs and adjust types entry points (#4824)Work in this release contributed by @MikevPeeren. Thank you for your contribution!
isNaN function (#4759)This release fixes a bug from 6.19.0 causing type import errors in most JS SDKs.
This release makes a change to the data normalization process, limiting the number of entries or properties which will
be included in any given array or object to 1000. Previously there was no limit, so in rare cases you may notice a
change in your context data. If this is a problem, you can increase the limit with the new maxNormalizationBreadth
setting. See #4689 for details.
normalize maximum properties/elements (#4689)apply rather than call in try-catch integration (#4695)@sentry/browser (#4688)syntheticException creation (#4691)BrowserTracing logging flag default value (#4708)isDebugBuild logging guard (#4696)Work in this release contributed by @Turbo87. Thank you for your contribution!
If you are using @sentry-internal/eslint-config-sdk, please note that this release turns on the
quotes rule to enforce usage of single quotes.
This release also removes @sentry/tracing as a dependency of @sentry/node. Please explicitly install and import
@sentry/tracing if you want to use performance monitoring capabilities. For more details,
see our docs on setting up Node Performance Monitoring.
We also now produce an ES6 version of our
CDN tracing bundle, which can be accessed
with bundle.tracing.es6.min.js.
Work in this release contributed by @Ignigena. Thank you for your contribution!
Work in this release contributed by @belgattitude, @pbernery, and @kylemh. Thank you for your contributions!
This patch deprecates the frameContextLines option for the Node SDK. The
migration documentation details how to migrate off the deprecated
frameContextLines option.
ignoreSentryErrors option for AWS lambda (#4620)Work in this release contributed by @GoshaEgorian and @ichina. Thank you for your contributions!
Work in this release contributed by @aaronadamsCA. Thank you for your contribution!
normalizeDepth when normalization is skipped(#4574)Work in this release contributed by @mydea. Thank you for your contribution!
Work in this release contributed by @connorjclark. Thank you for your contribution!
Work in this release contributed by @mobilestar1. Thank you for your contribution!
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.
@sentry/webpack-plugin to 1.18.5 (#4501)@sentry/utils (#4492)Work in this release contributed by @Bobakanoosh and @ssnielsen. Thank you for your contributions!
@sentry/webpack-plugin from 1.18.3 to 1.18.4 (#4464)ExtraErrorData's depth option (#4487)BrowserTracing integration directly (#4480)SpanStatus enum (#4478)_isVue not defined in Vue3 (#4461)Work in this release contributed by @7inspire, @jaeseokk, and @rchl. Thank you for your contributions!
req and res if necessary when instrumenting server (#4467)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.
rethrowAfterCapture use in AWS lambda wrapper (#4448)is casting (#4451)hidden-source-map as webpack devtool value (#4436)Work in this release contributed by @datbth. Thank you for your contribution!
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.
Work in this release contributed by @yordis, @Badisi, and @lh1me. Thank you for your contribution!
Work in this release contributed by @KATT. Thank you for your contribution!
Work in this release contributed by @jherdman and @travigd. Thank you for your contribution!
DOMExceptions, if possible (#4160)withSentry is done (#4027)Work in this release contributed by @nowylie. Thank you for your contribution!
is utility functions (#4124)false API resolved without sending a response warning (#4139)is utility functions (#4124)Work in this release contributed by @J4YF7O. Thank you for your contribution!
Work in this release contributed by @tmilar, @deammer, and @freekii. Thank you for your contributions!
@sentry/xxxx packages (#4019)distDir Next.js option (#3990)document.head or document.body exists for injectReportDialog (#3972)safari(-web)-extension stack (#3929)ember-source to devDependencies (#3962)lastEventID for transactions (#3966)basePath on urlPrefix (#3922)autoSessionTracking if dsn undefined (#3954)flush and close when client undefined (#3846)SentryWebpackPlugin from uploading unnecessary files (#3845)Event objects (#3864)Vue 3 (#3804)web-vitals 2.1.0 (#3781)InitSentryForEmber optional (#3802)flush finish in API routes (#3811)domains to prevent scope bleed (#3788)Route typing more generic (#3809)ensureNoCircularStructures experiment to help debug serialization bugs (#3776)ErrorBoundary (#3793)withSentryConfig return type match given config type (#3760)captureRequestSession is available before its called (#3773)autoSessionTracking correctly (#3758)allRoutes cannot triple equal a new array instance (#3779)document.scripts in metrics (#3766)ExtractedNodeRequestData to include valid query_params for tracesSampler (#3715)_app and API routes (#3786)productionBrowserSourceMaps in config (#3765)beforeSend more strict (#3713)withSentryConfig (#3698)entry property (#3703)request context (#3672)tunnel option to support request tunneling for dealing with ad-blockers (#3521)UrlParser in Node.js transports (#3612)serializeAttribute option to DOM breadcrumbs. (#3620)Improve NextConfigExports compatibility (#3592)trace directive (#3617)performance.now when calculating browser timing (#3657)exception and stacktrace events (#3653)require(console) with a global object (#3623)HTTPModule more abstract to be able to use it in non-Node.JS environments (#3655)BrowserTracing integration directly from @sentry/nextjs (#3647)require calls in config code (#3426)SentryRequestType to RateLimitingCategory mapping (#3328)fetchImpl and cleanup redundant iframe (#3341)req.baseUrl is empty (#3329)@sentry/node (#3335)Connection.createQuery instead of Connection.prototype.query (#3353)BrowserTracing integration (#3338)NodeClient/BrowserClient to protect it from being overwritten by
other classes extending BaseClient like @sentry/serverless (#3279)find method from mongo tracing list (#3253)spanRecorder whenever transactions are sampled (#3255)file:// protocol (#3264)sentry-trace header (#3261)We updated the way how we calculate errored and crashed sessions with this update. Please be aware that some numbers might change for you and they now should reflect the actual reality. Visit our docs for more information.
user to publicKey in Dsn type and class (#3225)startTransaction is called (#3210)vue-router to peerDependencies list (#3214)/dist didn't exist before building (#3190)This major version release doesn't contain any breaking API/code changes. Starting from the version 6.0.0, all SDKs
that support sending sessions data will do so by default. See our
Release Health docs to learn more. As of this version, it applies to
all Browser SDKs (Browser, React, Angular, Vue, Gatsby etc.). Node.js and other related Server SDKs will follow soon
after, in the minor 6.x release. You can opt-out of this behavior by setting autoSessionTracking: false option
during SDK initialization.
@sentry/wasm package (#3080)