-
Notifications
You must be signed in to change notification settings - Fork 0
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/react to v8.32.0 #156
Merged
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
changed the title
fix(deps): update dependency @sentry/react to v8.12.0
fix(deps): update dependency @sentry/react to v8.13.0
Jun 27, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
June 27, 2024 13:31
0dd3329
to
3c53c13
Compare
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
July 5, 2024 23:12
3c53c13
to
b21522e
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.13.0
fix(deps): update dependency @sentry/react to v8.15.0
Jul 5, 2024
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.15.0
fix(deps): update dependency @sentry/react to v8.16.0
Jul 9, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
2 times, most recently
from
July 10, 2024 14:28
6094df0
to
26d11d7
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.16.0
fix(deps): update dependency @sentry/react to v8.17.0
Jul 10, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
July 16, 2024 16:53
26d11d7
to
a7e62ee
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.17.0
fix(deps): update dependency @sentry/react to v8.18.0
Jul 16, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
July 19, 2024 13:31
a7e62ee
to
12c1e95
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.18.0
fix(deps): update dependency @sentry/react to v8.19.0
Jul 19, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
July 24, 2024 19:50
12c1e95
to
c77e53a
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.19.0
fix(deps): update dependency @sentry/react to v8.20.0
Jul 24, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
July 31, 2024 12:39
c77e53a
to
cd93d0f
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.20.0
fix(deps): update dependency @sentry/react to v8.21.0
Jul 31, 2024
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.21.0
fix(deps): update dependency @sentry/react to v8.22.0
Aug 1, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
2 times, most recently
from
August 5, 2024 14:30
eb8126c
to
40e87c3
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.22.0
fix(deps): update dependency @sentry/react to v8.23.0
Aug 5, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
August 6, 2024 13:52
40e87c3
to
f5cea5e
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.23.0
fix(deps): update dependency @sentry/react to v8.24.0
Aug 6, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
August 9, 2024 08:45
f5cea5e
to
248dcae
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.24.0
fix(deps): update dependency @sentry/react to v8.25.0
Aug 9, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
August 14, 2024 09:49
248dcae
to
08676e6
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.25.0
fix(deps): update dependency @sentry/react to v8.26.0
Aug 14, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
August 27, 2024 14:33
08676e6
to
24adb47
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.26.0
fix(deps): update dependency @sentry/react to v8.27.0
Aug 27, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
September 3, 2024 12:52
24adb47
to
d9b188c
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.27.0
fix(deps): update dependency @sentry/react to v8.28.0
Sep 3, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
September 9, 2024 10:58
d9b188c
to
bcc069b
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.28.0
fix(deps): update dependency @sentry/react to v8.29.0
Sep 9, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
September 10, 2024 17:25
bcc069b
to
71a555c
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.29.0
fix(deps): update dependency @sentry/react to v8.30.0
Sep 10, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
September 23, 2024 10:13
71a555c
to
80bd0b8
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.30.0
fix(deps): update dependency @sentry/react to v8.31.0
Sep 23, 2024
renovate
bot
force-pushed
the
renovate/sentry-packages
branch
from
September 25, 2024 14:26
80bd0b8
to
96d9809
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/react to v8.31.0
fix(deps): update dependency @sentry/react to v8.32.0
Sep 25, 2024
Quality Gate passedIssues Measures |
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:
8.11.0
->8.32.0
Release Notes
getsentry/sentry-javascript (@sentry/react)
v8.32.0
Compare Source
Important Changes
Moves the description of navigation related browser spans into the op, e.g. browser - cache -> browser.cache and sets
the description to the performanceEntry objects' names (in this context it is the URL of the page).
feat(node): Add amqplibIntegration (#13714)
feat(nestjs): Add
SentryGlobalGenericFilter
and allow specifying application ref in global filter (#13673)Adds a
SentryGlobalGenericFilter
that filters both graphql and http exceptions depending on the context.Sets log levels in breadcrumbs for 5xx to error and 4xx to warning.
Other Changes
sampled
flag from dynamic sampling context in Tracing without Performance mode (#13753)Work in this release was contributed by @Zen-cronic and @Sjoertjuh. Thank you for your contributions!
v8.31.0
Compare Source
Important Changes
dataloader
integration (#13664)This release adds a new integration for the
dataloader
package. The NodeSDK (and all SDKs that depend on it) will now automatically instrument
dataloader
instances. You can also add itmanually:
Other Changes
activationStart
timestamp to pageload span (#13658)deleteSourcemapsAfterUpload
(#13610)http.server.prefetch
op (#13600)disableInstrumentationWarnings
option (#13693)experimental_basicServerTracing
option to Nuxt module (#13643)onError
callback + other small improvements to debugging (#13721)consoleSandbox
(#13690)lazyLoadIntegration
script parent element lookup (#13717)SentryTraced
functions (#13684)Propagator.inject
(#13381)Work in this release was contributed by @KyGuy2002, @artzhookov, and @julianCast. Thank you for your contributions!
v8.30.0
Compare Source
Important Changes
kafkajs
integration (#13528)This release adds a new integration that instruments
kafkajs
library with spans and traces. This integration isautomatically enabled by default, but can be included with the
Sentry.kafkaIntegration()
import.Other Changes
@opentelemetry/instrumentation-undici
for fetch tracing (#13485)trackComponents
list matches components with or without<>
(#13543)Work in this release was contributed by @Zen-cronic and @odanado. Thank you for your contributions!
v8.29.0
Compare Source
Important Changes
This release marks the beta releases of the
@sentry/solid
and@sentry/solidstart
Sentry SDKs. For details on how touse them, check out the
Sentry Solid SDK README and the
Sentry SolidStart SDK README
respectively. Please reach out on GitHub if you have
any feedback or concerns.
Adds the SDK option to only wrap ES modules with
import-in-the-middle
that specifically need to be instrumented.All internal OpenTelemetry instrumentation was updated to their latest version. This adds support for Mongoose v7 and v8
and fixes various bugs related to ESM mode.
Other Changes
generic-pool
integration (#13465)browserTracingIntegration
by default (#13561)sentrySolidStartVite
plugin to simplify source maps upload (#13493)context.waitUntil
call in request handler (#13549)generic-pool
span origins with underscores (#13579)Work in this release was contributed by @Zen-cronic. Thank you for your contribution!
v8.28.0
Compare Source
Important Changes
This release contains the beta version of
@sentry/nestjs
! For details on how to use it, check out theREADME. Any feedback/bug reports
are greatly appreciated, please reach out on GitHub.
This release fixes a bug in the
@sentry/browser
package and all SDKs depending on this package (e.g.@sentry/react
or
@sentry/nextjs
) that caused the SDK to send incorrect web vital values for the LCP, FCP and FP vitals. The SDKpreviously incorrectly processed the original values as they were reported from the browser. When updating your SDK to
this version, you might experience an increase in LCP, FCP and FP values, which potentially leads to a decrease in your
performance score in the Web Vitals Insights module in Sentry. This is because the previously reported values were
smaller than the actually measured values. We apologize for the inconvenience!
Other Changes
SentryGlobalGraphQLFilter
(#13545)bundleSizeOptimizations
to build options (#13323)captureRequestError
(#13550)@Injectable
(#13544)Work in this release was contributed by @leopoldkristjansson, @mhuggins and @filips123. Thank you for your
contributions!
v8.27.0
Compare 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
SentryModule
to yourapplication, which led to issues in certain scenarios. You will now have to either add the
SentryGlobalFilter
toyour 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.0
Compare Source
Important Changes
feat(node): Add
fsInstrumentation
(#13291)This release adds
fsIntegration
, an integration that instruments thefs
API 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.init
call. 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
getTraceData
implementation (#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_captureRequestError
to reflectRequestInfo.path
change 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
origin
is 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.0
Compare 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
bundleSizeOptimizations
vite options to integration (#13250)getTraceMetaTags
function (#13201)useOperationNameForRootSpan
tographqlIntegration
(#13248)wrapServerRouteWithSentry
wrapper (#13247)context
overevent
(#13266)defaultIntegrations: undefined
(#13261)v8.24.0
Compare Source
v8.23.0
Compare Source
Important Changes
This release includes support for Cloudflare D1, Cloudflare's serverless SQL database. To instrument your Cloudflare D1
database, use the
instrumentD1WithSentry
method as follows:Other Changes
getTraceData
function (#13134)onBeforeResponse
middleware to enable distributed tracing (#13221)window
global scopes (#13156)\_loadAndRenderDialog
(#13203)Work in this release was contributed by @horochx. Thank you for your contribution!
v8.22.0
Compare 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_error
client report happens (#13072)globalThis
for code injection (#13132)v8.21.0
Compare Source
Important Changes
withSentry
method (#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.0
Compare Source
Important Changes
registerEsmLoaderHooks
to preload (#12998)You can write your own custom preload script and configure this in the preload options.
registerEsmLoaderHooks
can 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.0
Compare Source
node --import=@sentry/node/import app.js
v8.18.0
Compare Source
Important Changes
enableTracing
(12897)The
enableTracing
option has been deprecated and will be removed in the next major version. We recommend removing itin favor of the
tracesSampleRate
andtracesSampler
options. If you want to enable performance monitoring, please setthe
tracesSampleRate
to a sample rate of your choice, or provide a sampling function astracesSampler
optioninstead. If you want to disable performance monitoring, remove the
tracesSampler
andtracesSampleRate
options.Other Changes
exclude
andinclude
options for ESM loader (#12910)experimental_captureRequestError
foronRequestError
hook (#12885)rrweb
to 2.25.0 (#12478)ErrorEvent
check in ErrorHandler to avoid throwing in Node environments (#12892)ignoreIncomingRequests
callback (#12929)otel.kind: INTERNAL
attribute (#12841)null
asparentSpan
instartSpan*
(#12928)Work in this release was contributed by @GitSquared and @mcous. Thank you for your contributions!
Bundle size 📦
v8.17.0
Compare Source
v8.16.0
Compare Source
Important Changes
Previously, the
@sentry/nextjs
SDK 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/nestjs
SDK now includes a@SentryCron
decorator that can be used to augment the native NestJS@Cron
decorator to send check-ins to Sentry before and after each cron job run:
Other Changes
httpIntegration
(#12761)addPluginTemplate
(#12760)h
import inScreenshotEditor
(#12784)autoSessionTracking
is enabled by default (#12790)v8.15.0
Compare Source
on
(#11710)spanTimeInputToSeconds
for 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.0
Compare Source
Important Changes
The
@sentry/nestjs
SDK no longer captures 4xx errors automatically.Other Changes
JSX
(#12691)registerEsmLoaderHooks
option (#12684)afterAllSetup
instead of next tick (#12709)Work in this release was contributed by @quisido. Thank you for your contribution!
v8.13.0
Compare 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)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC).
🚦 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.