Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.0.1
->2.1.1
0.0.8
->0.3.3
8.2.1
->8.4.0
10.1.0
->10.1.1
7.43.0
->7.73.0
1.0.1
->1.0.3
18.15.3
->18.18.4
9.0.1
->9.0.5
16.0.3
->16.3.1
1.1.0
->1.3.6
8.36.0
->8.51.0
4.14.1
->4.23.2
13.2.0
->13.3.0
2.0.21
->2.0.22
7.3.4
->7.4.1
8.11.0
->8.16.0
10.0.0
->10.2.3
8.1.1
->8.9.0
2.8.4
->2.8.8
1.9.1
->1.27.1
2.8.1
->2.9.0
4.1.2
->4.2.0
3.12.5
->3.13.0
5.0.2
->5.2.2
9.0.0
->9.0.1
0.29.3
->0.34.6
Release Notes
BeeeQueue/eslint-plugin (@beequeue/eslint-plugin)
v2.1.1
Compare Source
Patch Changes
7c91bed
- Update dependencies and plugins7c91bed
- Fixed error with todo comments rulev2.1.0
Compare Source
Minor Changes
#44
564855d
- Addedesm-extensions
rule for automatically adding.js
extensions to files.#44
564855d
- Addedesm
preset for ESM projects.Patch Changes
564855d
- Replacedeslint-plugin-import
with fastereslint-plugin-i
.edgedb/edgedb-js (@edgedb/generate)
v0.3.3
Compare Source
v0.3.2
Compare Source
v0.3.1
Compare Source
v0.3.0
Compare Source
v0.2.1
Compare Source
v0.2.0
Compare Source
v0.1.1
Compare Source
v0.1.0
Compare Source
fastify/fastify-cors (@fastify/cors)
v8.4.0
Compare Source
What's Changed
Object.assign()
by @Fdawgs in https://github.com/fastify/fastify-cors/pull/257node:
prefix to bypass require.cache call for builtins by @Fdawgs in https://github.com/fastify/fastify-cors/pull/269New Contributors
Full Changelog: fastify/fastify-cors@v8.3.0...v8.4.0
v8.3.0
Compare Source
What's Changed
cacheControl
to control caching in CDN by @brettwillis in https://github.com/fastify/fastify-cors/pull/252New Contributors
Full Changelog: fastify/fastify-cors@v8.2.1...v8.3.0
fastify/fastify-helmet (@fastify/helmet)
v10.1.1
Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify-helmet@v10.1.0...v10.1.1
getsentry/sentry-javascript (@sentry/node)
v7.73.0
Compare Source
Important Changes
This is fully backwards compatible with prior versions of the Replay SDK. The only breaking change that we will making is to not be masking
aria-label
by default. The reason for this change is to align with our core SDK which also does not maskaria-label
. This change also enables better support of searching by clicks.Another change that needs to be highlighted is the 13% bundle size increase. This bundle size increase is necessary to bring improved recording performance and improved replay fidelity, especially in regards to web components and iframes. We will be investigating the reduction of the bundle size in this PR.
Here are benchmarks comparing the version 1 of rrweb to version 2
Other Changes
captureAllExceptions
by default (#9102)tunnel
is considered forisSentryUrl
checks (#9130)RequestAsyncStorage
fallback path (#9126)load
functions (#9071)InboundFilters
integration to useprocessEvent
(#9020)processEvent
(#9019)Work in this release contributed by @vlad-zhukov. Thank you for your contribution!
Bundle size 📦
v7.72.0
Compare Source
Important Changes
This release introduces support for Application Not Responding (ANR) errors for Node.js applications.
These errors are triggered when the Node.js main thread event loop of an application is blocked for more than five seconds.
The Node SDK reports ANR errors as Sentry events and can optionally attach a stacktrace of the blocking code to the ANR event.
To enable ANR detection, import and use the
enableANRDetection
function from the@sentry/node
package before you run the rest of your application code.Any event loop blocking before calling
enableANRDetection
will not be detected by the SDK.Example (ESM):
Example (CJS):
Other Changes
RequestAsyncStorage
locations by locations that webpack will resolve (#9114)replay_id
is not captured when session is expired (#9109)v7.71.0
Compare Source
basename
-prefixed route. (#9076)processEvent
(#9022)Work in this release contributed by @jorrit. Thank you for your contribution!
v7.70.0
Compare Source
Important Changes
This release contains the beta version of
@sentry/bun
, our SDK for the Bun JavaScript runtime! For details on how to use it, please see the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.Note that as of now the Bun runtime does not support global error handlers. This is being actively worked on, see the tracking issue in Bun's GitHub repo.
The Sentry Remix SDK now officially supports Remix v2! See our Remix docs for more details.
Other Changes
processEvent
hook onIntegration
(#9017)React.ComponentType
instead ofReact.FC
aswithSentry
's generic type. (#9043)preprocessEvent
hook (#9034)handleErrorWithSentry
type (#9054)Work in this release contributed by @Dima-Dim, @krist7599555 and @lifeiscontent. Thank you for your contributions!
Special thanks for @isaacharrisholt for helping us implement a Vercel Edge Runtime SDK which we use under the hood for our Next.js SDK.
Bundle size 📦
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)Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.