Update dependency @sentry/nextjs to v10.13.0 #293
Merged
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.
Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.
This PR contains the following updates:
10.12.0->10.13.010.15.0(+1)Release Notes
getsentry/sentry-javascript (@sentry/nextjs)
v10.13.0Compare Source
Important Changes
feat(browser): Add option to explicitly end pageload span via
reportPageLoaded()(#17697)With this release you can take manual control of ending the pageload span. Usually this span is ended automatically by the SDK, based on a period of inactivity after the initial page was loaded in the browser. If you want full control over the pageload duration, you can tell Sentry, when your page was fully loaded:
Note that if
Sentry.reportPageLoaded()is not called within 30 seconds of the initial pageload (or whatever value thefinalTimeoutoption is set to), the pageload span will be ended automatically.feat(core,node): Add instrumentation for
GoogleGenerativeAI(#17625)The SDK now automatically instruments the
@google/generative-aipackage to provide insights into your AI operations.feat(nextjs): Promote
useRunAfterProductionCompileHookto non-experimental build option (#17721)The
useRunAfterProductionCompileHookoption is no longer experimental and is now a stable build option for Next.js projects.feat(nextjs): Use
afterProductionCompilehook for webpack builds (#17655)Next.js projects using webpack can opt-in to use the
useRunAfterProductionCompileHookhook for source map uploads.feat(nextjs): Flip default value for
useRunAfterProductionCompileHookfor Turbopack builds (#17722)The
useRunAfterProductionCompileHookoption is now enabled by default for Turbopack builds, enabling automated source map uploads.feat(node): Do not drop 300 and 304 status codes by default (#17686)
HTTP transactions with 300 and 304 status codes are now captured by default, providing better visibility into redirect and caching behavior.
Other Changes
onSuccesstohandleCallbackErrors(#17679)consoleLoggingIntegration(#17703)oscontext (#17720)thirdPartyErrorFilterIntegration(#17693)thiscontext for vercel AI instrumentation (#17681)Internal Changes
reportPageLoaded(#17724)getTestMatrix(#17673)SyncPromisewhere not needed (#17641)ignoreSpans(#17692)module_metadataassignment and cleanup functions (#17696)HandleDocumentRequestFunction(#17680)Work in this release was contributed by @Olexandr88. Thank you for your contribution!
Bundle size 📦
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 is behind base branch, 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.