-
-
Notifications
You must be signed in to change notification settings - Fork 15
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/nextjs to v8.22.0 #496
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/sentry-javascript-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
🌐 Branch deployed as preview to: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Device | URL |
---|---|
desktop | https://preview.coh3stats.com |
Device | URL |
---|---|
mobile | https://preview.coh3stats.com |
Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead
6b2e3a9
to
dc86f1b
Compare
dc86f1b
to
ef6a4ac
Compare
ef6a4ac
to
71e126f
Compare
71e126f
to
0179108
Compare
0179108
to
88ab794
Compare
88ab794
to
5d02145
Compare
5d02145
to
9196c8e
Compare
9196c8e
to
e4956c2
Compare
e4956c2
to
5f69a47
Compare
5f69a47
to
5a0676a
Compare
5a0676a
to
ac20413
Compare
f3f065c
to
8a15212
Compare
8a15212
to
bb809b8
Compare
bb809b8
to
acec696
Compare
acec696
to
dd096d8
Compare
dd096d8
to
0fe4a55
Compare
0fe4a55
to
845c275
Compare
845c275
to
893287e
Compare
893287e
to
5831c1a
Compare
5831c1a
to
300b839
Compare
300b839
to
fd5a496
Compare
fd5a496
to
0b60709
Compare
0b60709
to
9ebcdc6
Compare
9ebcdc6
to
a1953ef
Compare
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.5.0
->8.22.0
Release Notes
getsentry/sentry-javascript (@sentry/nextjs)
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)v8.12.0
Compare Source
Important Changes
This release introduces breaking changes to the
@sentry/solid
package (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
. ImportsolidRouterBrowserTracingIntegration
from@sentry/solid/solidrouter
and add it toSentry.init
Sentry.init()
now returns a client directly, so you don't need to explicitly callgetClient()
anymore:deleteSourcemapsAfterUpload
option (#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)isRemixV2
as optional in exposed types. (#12614)Work in this release was contributed by @n4bb12. Thank you for your contribution!
v8.11.0
Compare Source
Important Changes
parentSpan
option 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/node
exports from framework SDKs. (#12589)Bundle size 📦
v8.10.0
Compare 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.
wrapExpressCreateRequestHandler
anymore. Additionally, the quality of thecaptured data improves. The old way to use
@sentry/remix
continues to work, but it is encouraged to use the new setup.Other Changes
thirdPartyErrorFilterIntegration
from@sentry/browser
(#12512)tags
field to any feedback config param (#12197)getDynamicSamplingContextFromSpan
(#12522)captureRemixServerException
from client SDK (#12497)Work in this release was contributed by @AndreyKovanov and @kiliman. Thank you for your contributions!
v8.9.2
Compare Source
v8.9.1
Compare 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
op
to 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.0
Compare Source
This upgrades the OpenTelemetry dependencies to the latest versions and makes OTEL use
import-in-the-middle
v1.8.0
.This should fix numerous issues with using OTEL instrumentation with ESM.
High level issues fixed with OTEL + ESM:
tsx
or similar libraries.date-fns
.openai
.ENOENT: no such file or directory
bugs that libraries likediscord.js
surface.
If you are still encountering issues with OpenTelemetry instrumentation and ESM, please let us know.
2.18.0
(#12381)thirdPartyErrorFilterIntegration
(#12267)mget
command in caching functionality (#12380)clientTraceMetadata
option (#12323)sentry
property on Next.js config object (#12366)(#12360)
v8.7.0
Important Changes
feat(react): Add TanStack Router integration (#12095)
This release adds instrumentation for TanStack router with a new
tanstackRouterBrowserTracingIntegration
in the@sentry/react
SDK:Other Changes
sourceMappingURL
comment on client whennextConfig.productionBrowserSourceMaps: true
isset (#12278)
v8.6.0
Important Changes
feat(metrics): Add
timings
method to metrics (#12226)This introduces a new method,
metrics.timing()
, which can be used in two ways:second
as unit:create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds:
feat(react): Add
Sentry.reactErrorHandler
(#12147)This PR introduces
Sentry.reactErrorHandler
, which you can use in React 19 as follows:For more details, take a look at the PR. Our
documentation will be updated soon!
Other Changes
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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 was generated by Mend Renovate. View the repository job log.