You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or 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
feat(integrations): Add ContextLines integration for html-embedded JS stack frames (#8699)
This release adds the ContextLines integration as an optional integration for the Browser SDKs to @sentry/integrations.
This integration adds source code from inline JavaScript of the current page's HTML (e.g. JS in <script> tags) to stack traces of captured errors.
It can't collect source code from assets referenced by your HTML (e.g. <script src="..." />).
The ContextLines integration is useful when you have inline JS code in HTML pages that can't be accessed by Sentry's backend, for example, due to a login-protected page.
import{ContextLines}from"@sentry/integrations";Sentry.init({// ...integrations: [newContextLines({// The number of lines to collect before and after each stack frame's line number// Defaults to 7frameContextLines: 7,}),],});
Other Changes
fix(nextjs): Make all wrappers isomorphic and available in all runtimes (#8743)
fix(replay): Cancel debounce when replay is too short/long (#8742)
fix(utils): dirname and basename should handle Windows paths (#8737)
ref: Hoist flush, close, and lastEventId into @sentry/core (#8731)
ref(node): Don't call JSON.stringify on prisma client when logging (#8745)
feat(integrations): Add ContextLines integration for html-embedded JS stack frames (#8699)
This release adds the ContextLines integration as an optional integration for the Browser SDKs to @sentry/integrations.
This integration adds source code from inline JavaScript of the current page's HTML (e.g. JS in <script> tags) to stack traces of captured errors.
It can't collect source code from assets referenced by your HTML (e.g. <script src="..." />).
The ContextLines integration is useful when you have inline JS code in HTML pages that can't be accessed by Sentry's backend, for example, due to a login-protected page.
import{ContextLines}from"@sentry/integrations";Sentry.init({// ...integrations: [newContextLines({// The number of lines to collect before and after each stack frame's line number// Defaults to 7frameContextLines: 7,}),],});
Other Changes
fix(nextjs): Make all wrappers isomorphic and available in all runtimes (#8743)
fix(replay): Cancel debounce when replay is too short/long (#8742)
fix(utils): dirname and basename should handle Windows paths (#8737)
ref: Hoist flush, close, and lastEventId into @sentry/core (#8731)
ref(node): Don't call JSON.stringify on prisma client when logging (#8745)
7.61.1
feat(nextjs): Add AsyncLocalStorage async context strategy to edge SDK (#8720)
fix(core): Filter internal API frames for synthetic frames (#8710)
fix(integrations): Capture exception if any arg to console method is an error (#8671)
fix(node-experimental): Update auto integration lookup & readme (#8690)
fix(node): Add availablility check on current hub to Node ContextLines integration (#8715)
fix(replay): Ensure buffer sessions end after capturing an error (#8713)
fix(replay): Ensure buffer->session switch is reliable (#8712)
fix(replay): Ensure we debounce flush if replay too short (#8716)
fix(replay): Improve capture of errorIds/traceIds (#8678)
fix(tracing): Set correct parent span id on fetch sentry-trace header (#8687)
fix(utils): Avoid pre_context and context_line overlap if frame lineno is out of bounds (#8722)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Breaking changes1: Performance Monitoring not required for Distributed Tracing
This release adds support for distributed tracing without requiring performance monitoring to be active on the JavaScript SDKs (browser and node). This means even if there is no sampled transaction/span, the SDK will still propagate traces to downstream services. Distributed Tracing can be configured with the tracePropagationTargets option, which controls what requests to attach the sentry-trace and baggage HTTP headers to (which is what propagates tracing information).
2: Support AggregateErrors in LinkedErrors integration
This release adds support for AggregateErrors. AggregateErrors are considered as Exception Groups by Sentry, and will be visualized and grouped differently. See the Exception Groups Changelog Post for more details.
Exception Group support requires Self-Hosted Sentry version 23.5.1 or newer.
3: Add a new option networkDetailDenyUrls
This release adds a new option networkDetailDenyUrls to the Replay integration. This option allows you to specify a list of URLs that should not be captured by the Replay integration, which can be used alongside the existing networkDetailAllowUrls for finely grained control of which URLs should have network details captured.
Breaking changes1: Performance Monitoring not required for Distributed Tracing
This release adds support for distributed tracing without requiring performance monitoring to be active on the JavaScript SDKs (browser and node). This means even if there is no sampled transaction/span, the SDK will still propagate traces to downstream services. Distributed Tracing can be configured with the tracePropagationTargets option, which controls what requests to attach the sentry-trace and baggage HTTP headers to (which is what propagates tracing information).
2: Support AggregateErrors in LinkedErrors integration
This release adds support for AggregateErrors. AggregateErrors are considered as Exception Groups by Sentry, and will be visualized and grouped differently. See the Exception Groups Changelog Post for more details.
Exception Group support requires Self-Hosted Sentry version 23.5.1 or newer.
3: Add a new option networkDetailDenyUrls
This release adds a new option networkDetailDenyUrls to the Replay integration. This option allows you to specify a list of URLs that should not be captured by the Replay integration, which can be used alongside the existing networkDetailAllowUrls for finely grained control of which URLs should have network details captured.
Breaking changes1: Performance Monitoring not required for Distributed Tracing
This release adds support for distributed tracing without requiring performance monitoring to be active on the JavaScript SDKs (browser and node). This means even if there is no sampled transaction/span, the SDK will still propagate traces to downstream services. Distributed Tracing can be configured with the tracePropagationTargets option, which controls what requests to attach the sentry-trace and baggage HTTP headers to (which is what propagates tracing information).
2: Support AggregateErrors in LinkedErrors integration
This release adds support for AggregateErrors. AggregateErrors are considered as Exception Groups by Sentry, and will be visualized and grouped differently. See the Exception Groups Changelog Post for more details.
Exception Group support requires Self-Hosted Sentry version 23.5.1 or newer.
3: Add a new option networkDetailDenyUrls
This release adds a new option networkDetailDenyUrls to the Replay integration. This option allows you to specify a list of URLs that should not be captured by the Replay integration, which can be used alongside the existing networkDetailAllowUrls for finely grained control of which URLs should have network details captured.
Breaking changes1: feat(replay): Ensure min/max duration when flushing (#8596)
The replay feature will no longer send replays that are less than 5 seconds long. This is a breaking change if your application relies on short replays. You can configure the minimum replay duration, but it is capped at 15 seconds maximum. Refactor your code as follows if needed:
- new Replay({})+ new Replay({ minReplayDuration: 10000 }) // in ms
dependenciesPull requests that update a dependency file
0 participants
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.
dependabot
bot
added
the
dependencies
Bumps @sentry/node from 7.57.0 to 7.62.0.
Release notes
Sourced from
@sentry/node's releases.... (truncated)
Changelog
Sourced from
@sentry/node's changelog.... (truncated)
Commits
ba03f87release: 7.62.061cdc72Merge pull request #8763 from getsentry/prepare-release/7.62.0b114002Merge branch 'master' into prepare-release/7.62.051159b7chore(publish): Remove status provider setting from Craft config (#8762)4804882chore(publish): Try different status provider context (#8755)b986eaeMerge pull request #8754 from getsentry/prepare-release/7.62.09070e3eadd ContextLines description, apply feedback8a0a33cmeta: Update CHANGELOG for version 7.62.022a8addchore(ci): Addjob_required_jobs_passedas a status provider context (#8752)672e56cchore(ci): Make "Required Tests passed" job depend on artifact upload and oth...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)