fix(deps): update dependency @sentry/nextjs to v8 #84
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Report too large to display inline |
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
ffe471e
to
334bb58
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
334bb58
to
93176dd
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^7.100.1->^8.0.0Release Notes
getsentry/sentry-javascript (@sentry/nextjs)
v8.27.0Compare Source
Important Changes
fix(nestjs): Exception filters in main app module are not being executed (#13278)
With this release nestjs error monitoring is no longer automatically set up after adding the
SentryModuleto yourapplication, which led to issues in certain scenarios. You will now have to either add the
SentryGlobalFiltertoyour main module providers or decorate the
catch()method in your existing global exception filters with the newlyreleased
@WithSentry()decorator. See the docs formore details.
Other Changes
Deno.permissions.querySync(#13378)Work in this release was contributed by @charpeni. Thank you for your contribution!
v8.26.0Compare Source
Important Changes
feat(node): Add
fsInstrumentation(#13291)This release adds
fsIntegration, an integration that instruments thefsAPI to the Sentry Node SDK. Theintegration creates spans with naming patterns of
fs.readFile,fs.unlink, and so on.This integration is not enabled by default and needs to be registered in your
Sentry.initcall. You can configurevia options whether to include path arguments or error messages as span attributes when an fs call fails:
WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of
file I/O, like for example when running a framework dev server, including this integration can massively slow down
your application.
Other Changes
feat(browser): Add spotlightBrowser integration (#13263)
feat(browser): Allow sentry in safari extension background page (#13209)
feat(browser): Send CLS as standalone span (experimental) (#13056)
feat(core): Add OpenTelemetry-specific
getTraceDataimplementation (#13281)feat(nextjs): Always add
browserTracingIntegration(#13324)feat(nextjs): Always transmit trace data to the client (#13337)
feat(nextjs): export SentryBuildOptions (#13296)
feat(nextjs): Update
experimental_captureRequestErrorto reflectRequestInfo.pathchange in Next.js canary(#13344)
feat(nuxt): Always add tracing meta tags (#13273)
feat(nuxt): Set transaction name for server error (#13292)
feat(replay): Add a replay-specific logger (#13256)
feat(sveltekit): Add bundle size optimizations to plugin options (#13318)
feat(sveltekit): Always add browserTracingIntegration (#13322)
feat(tracing): Make long animation frames opt-out (#13255)
fix(astro): Correctly extract request data (#13315)
fix(astro): Only track access request headers in dynamic page requests (#13306)
fix(nuxt): Add import line for disabled
autoImport(#13342)fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)
fix(opentelemetry): Do not overwrite http span name if kind is internal (#13282)
fix(remix): Ensure
originis correctly set for remix server spans (#13305)Work in this release was contributed by @MonstraG, @undead-voron and @Zen-cronic. Thank you for your contributions!
v8.25.0Compare Source
Important Changes
This release contains the alpha version of
@sentry/solidstart, our SDK for Solid Start!For details on how to use it, please see the README. Any feedback/bug reports are
greatly appreciated, please reach out on GitHub.
Other Changes
bundleSizeOptimizationsvite options to integration (#13250)getTraceMetaTagsfunction (#13201)useOperationNameForRootSpantographqlIntegration(#13248)wrapServerRouteWithSentrywrapper (#13247)contextoverevent(#13266)defaultIntegrations: undefined(#13261)v8.24.0Compare Source
v8.23.0Compare Source
Important Changes
This release includes support for Cloudflare D1, Cloudflare's serverless SQL database. To instrument your Cloudflare D1
database, use the
instrumentD1WithSentrymethod as follows:Other Changes
getTraceDatafunction (#13134)onBeforeResponsemiddleware to enable distributed tracing (#13221)windowglobal scopes (#13156)\_loadAndRenderDialog(#13203)Work in this release was contributed by @horochx. Thank you for your contribution!
v8.22.0Compare Source
Important Changes
This release adds support for Cloudflare Pages to
@sentry/cloudflare, our SDK for theCloudflare Workers 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.
Other Changes
internal_sdk_errorclient report happens (#13072)globalThisfor code injection (#13132)v8.21.0Compare Source
Important Changes
withSentrymethod (#13025)This release contains the alpha version of
@sentry/cloudflare, our SDK for theCloudflare Workers 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.
Please note that only Cloudflare Workers are tested and supported - official Cloudflare Pages support will come in an
upcoming release.
Other Changes
beforeSendTransaction(#13022)v8.20.0Compare Source
Important Changes
registerEsmLoaderHooksto preload (#12998)You can write your own custom preload script and configure this in the preload options.
registerEsmLoaderHookscan bepassed as an option to
preloadOpenTelemetry, which allows to exclude/include packages in the preload.Sentry will not emit "fetch" spans if tracing is disabled. This is relevant for user who use their own sampler.
Other Changes
v8.19.0Compare Source
node --import=@sentry/node/import app.js
v8.18.0Compare Source
Important Changes
enableTracing(12897)The
enableTracingoption has been deprecated and will be removed in the next major version. We recommend removing itin favor of the
tracesSampleRateandtracesSampleroptions. If you want to enable performance monitoring, please setthe
tracesSampleRateto a sample rate of your choice, or provide a sampling function astracesSampleroptioninstead. If you want to disable performance monitoring, remove the
tracesSamplerandtracesSampleRateoptions.Other Changes
excludeandincludeoptions for ESM loader (#12910)experimental_captureRequestErrorforonRequestErrorhook (#12885)rrwebto 2.25.0 (#12478)ErrorEventcheck in ErrorHandler to avoid throwing in Node environments (#12892)ignoreIncomingRequestscallback (#12929)otel.kind: INTERNALattribute (#12841)nullasparentSpaninstartSpan*(#12928)Work in this release was contributed by @GitSquared and @mcous. Thank you for your contributions!
Bundle size 📦
v8.17.0Compare Source
v8.16.0Compare Source
Important Changes
Previously, the
@sentry/nextjsSDK automatically recorded spans in the form of transactions for each of your top-levelserver components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have
a root span, and more importantly, if you had data stream to the client, its duration was not captured because the
server component spans had finished before the data could finish streaming.
With this release, we will capture the duration of App Router requests in their entirety as a single transaction with
server component spans being descendants of that transaction. This means you will get more data that is also more
accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it
has before.
Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no
longer receive server component transactions like
Page Server Component (/path/to/route)(unless using the Edgeruntime), and you will instead receive transactions for your App Router SSR requests that look like
GET /path/to/route.If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.
The
@sentry/nestjsSDK now includes a@SentryCrondecorator that can be used to augment the native NestJS@Crondecorator to send check-ins to Sentry before and after each cron job run:
Other Changes
httpIntegration(#12761)addPluginTemplate(#12760)himport inScreenshotEditor(#12784)autoSessionTrackingis enabled by default (#12790)v8.15.0Compare Source
on(#11710)spanTimeInputToSecondsfor otel span exporter (#12699)lazyLoadIntegration(#12766)jsxRuntime: 'classic'to prevent breaking react 17 (#12775)getStack()(#12737)Work in this release was contributed by @arturovt and @jaulz. Thank you for your contributions!
v8.14.0Compare Source
Important Changes
The
@sentry/nestjsSDK no longer captures 4xx errors automatically.Other Changes
JSX(#12691)registerEsmLoaderHooksoption (#12684)afterAllSetupinstead of next tick (#12709)Work in this release was contributed by @quisido. Thank you for your contribution!
v8.13.0Compare Source
Important Changes
@sentry/nestjs)in alpha state. The SDK is a drop-in replacement for the Sentry Node SDK (
@sentry/node) supporting the same set offeatures. See the docs for how to use the SDK.
Other Changes
2.20.1(#12641)v8.12.0Compare Source
Important Changes
This release introduces breaking changes to the
@sentry/solidpackage (which is currently out in alpha).We've made it easier to get started with the solid router integration by removing the need to pass use* hooks
explicitly to
solidRouterBrowserTracingIntegration. ImportsolidRouterBrowserTracingIntegrationfrom@sentry/solid/solidrouterand add it toSentry.initSentry.init()now returns a client directly, so you don't need to explicitly callgetClient()anymore:deleteSourcemapsAfterUploadoption (#12457)This adds an easy way to delete sourcemaps immediately after uploading them:
maxSpanWaitDuration(#12610)Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before
discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is
necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing. However,
if you have very long-running spans in your application, a shorter duration might cause spans to be discarded too early.
In this case, you can increase this duration to a value that fits your expected data.
Other Changes
window.Sentry(#12580)isRemixV2as optional in exposed types. (#12614)Work in this release was contributed by @n4bb12. Thank you for your contribution!
v8.11.0Compare Source
Important Changes
parentSpanoption tostartSpan*APIs (#12567)We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to
explicitly manage the parent-child relationship of your spans better.
Other Changes
@sentry/nodeexports from framework SDKs. (#12589)Bundle size 📦
v8.10.0Compare Source
Important Changes
opentelemetry-instrumentation-remix. (#12110)You can now simplify your remix instrumentation by opting-in like this:
With this setup, you do not need to add e.g.
wrapExpressCreateRequestHandleranymore. Additionally, the quality of thecaptured data improves. The old way to use
@sentry/remixcontinues to work, but it is encouraged to use the new setup.Other Changes
thirdPartyErrorFilterIntegrationfrom@sentry/browser(#12512)tagsfield to any feedback config param (#12197)getDynamicSamplingContextFromSpan(#12522)captureRemixServerExceptionfrom client SDK (#12497)Work in this release was contributed by @AndreyKovanov and @kiliman. Thank you for your contributions!
v8.9.2Compare Source
v8.9.1Compare Source
Important changes
feat(solid): Add Solid SDK
This release adds a dedicated SDK for Solid JS in alpha state with instrumentation for
Solid Router and a custom
ErrorBoundary. See thepackage README for how to use
the SDK.
Other changes
opto Otel-generated lambda function root span (#12430)awslambda-auto(#12392)Work in this release was contributed by @soch4n. Thank you for your contribution!
v8.8.0Compare Source
This upgrades the OpenTelemetry dependencies to the latest versions and makes OTEL use
import-in-the-middlev1.8.0.This should fix numerous issues with using OTEL instrumentation with ESM.
High level issues fixed with OTEL + ESM:
tsxor similar libraries.date-fns.openai.ENOENT: no such file or directorybugs that libraries likediscord.jssurface.
If you are still encountering issues with OpenTelemetry instrumentation and ESM, please let us know.
2.18.0(#12381)thirdPartyErrorFilterIntegration(#12267)mgetcommand in caching functionality (#12380)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.