-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency @sentry/gatsby to v7.69.0 #1732
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
3c6d164
to
0e4e9bb
Compare
0e4e9bb
to
24bb4ba
Compare
24bb4ba
to
e2c4f2b
Compare
e2c4f2b
to
404e2f3
Compare
404e2f3
to
98cffe6
Compare
98cffe6
to
982940d
Compare
982940d
to
1f058cb
Compare
1b2bd62
to
870193e
Compare
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
870193e
to
fc60dca
Compare
fc60dca
to
4a98d84
Compare
4a98d84
to
dd02b01
Compare
dd02b01
to
bf68f6d
Compare
bf68f6d
to
9ed80e8
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update (7.69.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
7.20.0
->7.69.0
Release Notes
getsentry/sentry-javascript (@sentry/gatsby)
v7.69.0
Compare Source
Important Changes
This release introduces a new set of top level APIs for the Performance Monitoring SDKs. These aim to simplify creating spans and reduce the boilerplate needed for performance instrumentation. The three new methods introduced are
Sentry.startSpan
,Sentry.startInactiveSpan
, andSentry.startSpanManual
. These methods are available in the browser and node SDKs.Sentry.startSpan
wraps a callback in a span. The span is automatically finished when the callback returns. This is the recommended way to create spans.If you don't want the span to finish when the callback returns, use
Sentry.startSpanManual
to control when the span is finished. This is useful for event emitters or similar.Sentry.startSpan
andSentry.startSpanManual
create a span and make it active for the duration of the callback. Any spans created while this active span is running will be added as a child span to it. If you want to create a span without making it active, useSentry.startInactiveSpan
. This is useful for creating parallel spans that are not related to each other.Other Changes
BeforeFinishCallback
type (#8999)LinkedErrors
integration runs before all event processors (#8956)org
,project
andurl
as args to upload script (#8985)ignoreErrors
(#8986)pg
spans (#8993)useRoutes
(#8998)glob
to Remix SDK dependencies. (#8963)handleRecordingEmit
aborts when event is not added (#8938)Work in this release contributed by @Duncanxyz and @malay44. Thank you for your contributions!
v7.68.0
Compare Source
BroadcastChannel
andSharedWorker
to TryCatch EventTargets (#8943)name
toSpan
(#8949)ServerRuntimeClient
(#8930)span.finish()
works as expected (#8947)v7.67.0
Compare Source
Important Changes
TryCatch
integration as unhandled (#8890)HttpClient
andCaptureConsole
integrations as unhandled (#8891)This release fixes inconsistent behaviour of when our SDKs classify captured errors as unhandled.
Previously, some of our instrumentations correctly set unhandled, while others set handled.
Going forward, all errors caught automatically from our SDKs will be marked as unhandled.
If you manually capture errors (e.g. by calling
Sentry.captureException
), your errors will continue to be reported as handled.This change might lead to a decrease in reported crash-free sessions and consequently in your release health score.
If you have concerns about this, feel free to open an issue.
Other Changes
maxReplayDuration
(#8769)BrowserClientOptions
(#8921)wrap
function (#8927)Work in this release contributed by @SorsOps. Thank you for your contribution!
v7.66.0
Compare Source
package.json
exports (#8895)origin
to spans (#8765)v7.65.0
Compare Source
@sentry/vite-plugin
(#8877)Sentry.startActiveSpan
andSentry.startSpan
(#8803)AsyncLocalStorage
instance (#8831)requestAsyncStorageShim
path resolution on windows (#8875)OnUncaughtException
(#8876)wrapServerLoadWithSentry
(#8801)tracePropagationTargets
inBrowserTracing
(#8874)v7.64.0
Compare Source
v7.63.0
Compare Source
exceptionFromError
for use in hybrid SDKs (#8766)autoInstrumentServerFunctions
andautoInstrumentAppDirectory
(#8781)hasCheckout
handling (#8782)v7.62.0
Compare Source
Important Changes
ContextLines
integration for html-embedded JS stack frames (#8699)This release adds the
ContextLines
integration as an optional integration for the Browser SDKs to@sentry/integrations
.This integration adds source code from inline JavaScript of the current page's HTML (e.g. JS in
<script>
tags) to stack traces of captured errors.It can't collect source code from assets referenced by your HTML (e.g.
<script src="..." />
).The
ContextLines
integration is useful when you have inline JS code in HTML pages that can't be accessed by Sentry's backend, for example, due to a login-protected page.Other Changes
dirname
andbasename
should handle Windows paths (#8737)flush
,close
, andlastEventId
into@sentry/core
(#8731)JSON.stringify
on prisma client when logging (#8745)v7.61.1
Compare Source
AsyncLocalStorage
async context strategy to edge SDK (#8720)ContextLines
integration (#8715)pre_context
andcontext_line
overlap if frame lineno is out of bounds (#8722)v7.61.0
Compare Source
Important Changes
@sentry/node-experimental
package as MVP for POTEL (#8609)This introduces a new, experimental package,
@sentry/node-experimental
.This is a variant of the Node SDK which uses OpenTelemetry under the hood for performance instrumentation.
Note that this package is very much WIP, considered unstable and may change at any time.
No SemVer guarantees apply whatsoever. Still, if you're brave enough you can give it a try.
Read more about @sentry/node-experimental
Other Changes
v7.60.1
Compare Source
shift
pressed (#8648)session.started
for min/max duration check (#8617)v7.60.0
Compare Source
Important Changes
We will not send replays that are <5s long anymore. Additionally, we also added further safeguards to avoid overly long (>1h) replays.
You can optionally configure the min. replay duration (defaults to 5s):
Other Changes
v7.59.3
Compare Source
v7.59.2
Compare Source
No changes. This release was published to fix publishing issues with 7.59.0 and 7.59.1.
Please see 7.59.0 for the changes in that release.
v7.59.1
Compare Source
No changes. This release was published to fix a publishing issue with 7.59.0.
Please see 7.59.0 for the changes in that release.
v7.59.0
Compare Source
Important Changes
This release adds support for Remix v2 future flags, in particular for new error handling utilities of Remix v2. We heavily recommend you switch to using
v2_errorBoundary
future flag to get the best error handling experience with Sentry.To capture errors from v2 client-side ErrorBoundary, you should define your own
ErrorBoundary
inroot.tsx
and useSentry.captureRemixErrorBoundaryError
helper to capture the error.For server-side errors, define a
handleError
function in your server entry point and use theSentry.captureRemixServerException
helper to capture the error.For more details, see the Sentry Remix SDK documentation.
Other Changes
ModuleMetadata
integration (#8475)SentryWebpackPlugin
in dev mode (#8557)HTTP_URL
attribute for client requests (#8539)beforeAddRecordingEvent
callback (#8548)v7.58.1
Compare Source
v7.58.0
Compare Source
Important Changes
This release adds support for distributed tracing without requiring performance monitoring to be active on the JavaScript SDKs (browser and node). This means even if there is no sampled transaction/span, the SDK will still propagate traces to downstream services. Distributed Tracing can be configured with the
tracePropagationTargets
option, which controls what requests to attach thesentry-trace
andbaggage
HTTP headers to (which is what propagates tracing information).feat(tracing): Add tracing without performance to browser and client Sveltekit (#8458)
feat(node): Add tracing without performance to Node http integration (#8450)
feat(node): Add tracing without performance to Node Undici (#8449)
feat(node): Populate propagation context using env variables (#8422)
feat(core): Support
AggregateErrors
inLinkedErrors
integration (#8463)This release adds support for
AggregateErrors
. AggregateErrors are considered as Exception Groups by Sentry, and will be visualized and grouped differently. See the Exception Groups Changelog Post for more details.Exception Group support requires Self-Hosted Sentry version 23.5.1 or newer.
networkDetailDenyUrls
(#8439)This release adds a new option
networkDetailDenyUrls
to theReplay
integration. This option allows you to specify a list of URLs that should not be captured by theReplay
integration, which can be used alongside the existingnetworkDetailAllowUrls
for finely grained control of which URLs should have network details captured.Other Changes
getModule
for Electron SDK (#8488)user.id
to be a number (#8330)crossorigin
attribute on report dialog (#8424)tunnelRoute
when doing static exports (#8471)basePath
option fortunnelRoute
(#8454)basename
option ofcreateBrowserRouter
(#8457)@sentry/node
exports. (#8509)redirect
andcatch
responses (#8467)Work in this release contributed by @mrdulin, @donaldxdonald & @ziyad-elabid-nw. Thank you for your contributions!
v7.57.0
Compare Source
Important Changes
This release version bumps the internally used typescript version from 3.8.x to 4.9.x.
We use ds-downlevel to generate two versions of our types, one for >=3.8, one for >=4.9.
This means that this change should be fully backwards compatible and not have any noticable user impact,
but if you still encounter issues please let us know.
Instead of passing
tracePropagationTargets
to theBrowserTracing
integration, you can now define them on the top level:TryCatch
integration by default (#8367)The Angular and Angular-ivy SDKs will not install the TryCatch integration anymore by default.
This integration conflicted with the
SentryErrorHander
, sometimes leading to duplicated errors and/or missing data on events.When capturing non-errors via
Sentry.captureException()
, e.g.Sentry.captureException({ prop: "custom object" })
,we now generate a more helpful value for the synthetic exception. Instead of e.g.
Non-Error exception captured with keys: currentTarget, isTrusted, target, type
, you'll now get messages like:Other Changes
http.response.status_code
tospan.data
(#8366)trace
if tracing is enabled (#8357)clickCount
as optional (#8376)autoDiscoverNodePerformanceMonitoringIntegrations
from SDK (#8382)fetch
if the SDK client is valid (#8381)sessionStorage
check (#8394)v7.56.0
Compare Source
window.open
for slow clicks (#8308)debug_meta
before sending (#8347)next
in Vue router 4 instrumentation (#8351)v7.55.2
Compare Source
EventType
from@sentry-internal/rrweb
(#8334)v7.55.1
Compare Source
@sentry-internal/rrweb
(#8329)v7.55.0
Compare Source
v7.54.0
Compare Source
Important Changes
feat(core): Add default entries to
ignoreTransactions
for Healthchecks #8191All SDKs now filter out health check transactions by default.
These are transactions where the transaction name matches typical API health check calls, such as
/^.*healthy.*$/
or/^. *heartbeat.*$/
. Take a look at this list to learn which regexes we currently use to match transaction names.We believe that these transactions do not provide value in most cases and we want to save you some of your quota by filtering them out by default.
These filters are implemented as default values for the top level
ignoreTransactions
option.You can disable this filtering by manually specifiying the
InboundFilters
integration and setting thedisableTransactionDefaults
option:feat(replay): Add
mutationBreadcrumbLimit
andmutationLimit
to Replay Options (#8228)The previously experimental options
mutationBreadcumbLimit
andmutationLimit
have been promoted to regular Replay integration options.A high number of DOM mutations (in a single event loop) can cause performance regressions in end-users' browsers.
Use
mutationBreadcrumbLimit
to send a breadcrumb along with your recording if the mutation limit was reached.Use
mutationLimit
to stop recording if the mutation limit was reached.feat(sveltekit): Add source maps support for Vercel (lambda) (#8256)
The SvelteKit SDK can now be used if you deploy your SvelteKit app to Vercel.
By default, the SDK's Vite plugin will detect the used adapter and adjust the source map uploading config as necessary.
If you want to override the default adapter detection, you can specify the
adapter
option in thesentrySvelteKit
options:Currently, the Vite plugin will configure itself correctly for
@sveltejs/adapter-auto
,@sveltejs/adapter-vercel
and@sveltejs/adapter-node
.Important: The SvelteKit SDK is not yet compatible with Vercel's edge runtime.
It will only work for lambda functions.
Other Changes
loadContext
through wrapped document request function (#8268)magicast
to supportsatisfied
keyword (#8254)v7.53.1
Compare Source
os.uptime()
throwing because of EPERM (#8206)v7.53.0
Compare Source
beforeAddRecordingEvent
Replay option (#8124)withSentryConfig
isomorphic (#8166)maskFn
v7.52.1
Compare Source
v7.52.0
Compare Source
Important Next.js SDK changes:
This release adds support Vercel Cron Jobs in the Next.js SDK.
The SDK will automatically create Sentry Cron Monitors for your Vercel Cron Jobs configured via
vercel.json
when deployed on Vercel.You can opt out of this functionality by setting the
automaticVercelMonitors
option tofalse
:(Note: Sentry Cron Monitoring is currently in beta and subject to change. Help us make it better by letting us know what you think. Respond on GitHub or write to us at [email protected])
Other changes
ignoreErrors
check (#8089)addTracingExtensions
was not documented in MIGRATION.md (#8101)createCheckinEnvelope
to core package (#8082)v7.51.2
Compare Source
v7.51.1
Compare Source
load
when typed explicitly (#8049)Replay
rrweb
changes:@sentry-internal/rrweb
was updated from 1.106.0 to 1.108.0::
in CSS rule from Safari (#86)Work in this release contributed by @sreetamdas. Thank you for your contribution!
v7.51.0
Compare Source
Important Changes
load
functions with proxy module (#7994)@sentry/sveltekit
now auto-wrapsload
functions in+(page|layout).(ts|js)
files (universal loads)+(page|layout).server.(ts|js)
files (server-only loads)This means that you don't have to manually add the
wrapLoadWithSentry
andwrapServerLoadWithSentry
functions around your load functions. The SDK will not interfere with already wrappedload
functions.For more details, take a look at the Readme
peerDependencies
to Angular 16 (#8035)We now officially support Angular 16 in
@sentry/angular-ivy
.Note that
@sentry/angular
does not support Angular 16.Note: This release contains a bug with generating cron monitors. We recommend you upgrade the JS SDK to 7.51.1 or above to use cron monitoring functionality
This release adds Sentry cron monitoring support to the Node SDK.
Check-in monitoring allows you to track a job's progress by completing two check-ins: one at the start of your job and another at the end of your job. This two-step process allows Sentry to notify you if your job didn't start when expected (missed) or if it exceeded its maximum runtime (failed).
If your job execution fails, you can notify Sentry about the failure:
Additional Features and Fixes
http.method
to node http spans (#7991)RewriteFrames
(#7995)Integration
type declaration as union type (#8016)undefined
toundefined
instead of"[undefined]"
(#8017)Work in this release contributed by @srubin and @arjenbrandenburgh. Thank you for your contributions!
v7.50.0
Compare Source
Important Changes
sentryHandle
to a factory function (#7975)With this release, the Sveltekit SDK (@sentry/sveltekit) is promoted to Beta.
This means that we do not expect any more breaking changes.
The final breaking change is that
sentryHandle
is now a function.So in order to update to 7.50.0, you have to update your
hooks.server.js
file:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.