Skip to content
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 sentry packages to v7.61.0 (minor) #289

Merged
merged 1 commit into from
Aug 1, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 20, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/react (source) 7.57.0 -> 7.61.0 age adoption passing confidence
@sentry/tracing (source) 7.57.0 -> 7.61.0 age adoption passing confidence

Release Notes

getsentry/sentry-javascript (@​sentry/react)

v7.61.0

Compare Source

Important Changes
  • feat(node-experimental): Add @sentry/node-experimental package as MVP for POTEL (#​8609)

This introduces a new, experimental package, @sentry/node-experimental.
This is a variant of the Node SDK which uses OpenTelemetry under the hood for performance instrumentation.

Note that this package is very much WIP, considered unstable and may change at any time.
No SemVer guarantees apply whatsoever. Still, if you're brave enough you can give it a try.
Read more about @​sentry/node-experimental

Other Changes
  • fix(node): Don't set extra baggage headers (#​8657)
  • fix(tracing): Trim idle transaction spans if they exceed final timeout (#​8653)

v7.60.1

Compare Source

  • fix(nextjs): Match folder paths with trailing separator (#​8615)
  • fix(replay): Ignore clicks with shift pressed (#​8648)
  • fix(replay): Use session.started for min/max duration check (#​8617)

v7.60.0

Compare Source

Important Changes
  • feat(replay): Ensure min/max duration when flushing (#​8596)

We will not send replays that are <5s long anymore. Additionally, we also added further safeguards to avoid overly long (>1h) replays.
You can optionally configure the min. replay duration (defaults to 5s):

new Replay({
  minReplayDuration: 10000 // in ms - note that this is capped at 15s max!
})
Other Changes
  • fix(profiling): Align to SDK selected time origin (#​8599)
  • fix(replay): Ensure multi click has correct timestamps (#​8591)
  • fix(utils): Truncate aggregate exception values (LinkedErrors) (#​8593)

v7.59.3

Compare Source

  • fix(browser): 0 is a valid index (#​8581)
  • fix(nextjs): Ensure Webpack plugin is available after dynamic require (#​8584)
  • types(browser): Add browser profiling client options (#​8565)

v7.59.2

Compare Source

No changes. This release was published to fix publishing issues with 7.59.0 and 7.59.1.
Please see 7.59.0 for the changes in that release.

v7.59.1

Compare Source

No changes. This release was published to fix a publishing issue with 7.59.0.
Please see 7.59.0 for the changes in that release.

v7.58.1

Compare Source

  • fix(node): Set propagation context even when tracingOptions are not defined (#​8517)

v7.58.0

Compare Source

Important Changes
  • 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).

Sentry.init({
  tracePropagationTargets: ["third-party-site.com", /^https:\/\/yourserver\.io\/api/],
});
  • feat(tracing): Add tracing without performance to browser and client Sveltekit (#​8458)

  • feat(node): Add tracing without performance to Node http integration (#​8450)

  • feat(node): Add tracing without performance to Node Undici (#​8449)

  • feat(node): Populate propagation context using env variables (#​8422)

  • feat(core): Support AggregateErrors in LinkedErrors integration (#​8463)

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.

  • feat(replay): Add a new option networkDetailDenyUrls (#​8439)

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.

Sentry.init({
  integrations: [
    new Sentry.Integrations.Replay({
      networkDetailDenyUrls: [/^http:\/\/example.com\/test$/],
    }),
  ],
});
Other Changes
  • feat(core): Add helpers to get module metadata from injected code (#​8438)
  • feat(core): Add sampling decision to trace envelope header (#​8483)
  • feat(node): Add trace context to checkin (#​8503)
  • feat(node): Export getModule for Electron SDK (#​8488)
  • feat(types): Allow user.id to be a number (#​8330)
  • fix(browser): Set anonymous crossorigin attribute on report dialog (#​8424)
  • fix(nextjs): Ignore tunnelRoute when doing static exports (#​8471)
  • fix(nextjs): Use basePath option for tunnelRoute (#​8454)
  • fix(node): Apply source context to linked errors even when it is uncached (#​8453)
  • fix(node): report errorMiddleware errors as unhandled (#​8048)
  • fix(react): Add support for basename option of createBrowserRouter (#​8457)
  • fix(remix): Add explicit @sentry/node exports. (#​8509)
  • fix(remix): Don't inject trace/baggage to redirect and catch responses (#​8467)
  • fix(replay): Adjust slow/multi click handling (#​8380)

Work in this release contributed by @​mrdulin, @​donaldxdonald & @​ziyad-elabid-nw. Thank you for your contributions!


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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jul 20, 2023
@renovate renovate bot changed the title fix(deps): update sentry packages to v7.59.3 (minor) fix(deps): update sentry packages to v7.60.0 (minor) Jul 21, 2023
@renovate renovate bot force-pushed the renovate/sentry-packages branch from 3890b8b to d81aa07 Compare July 21, 2023 10:33
@renovate renovate bot changed the title fix(deps): update sentry packages to v7.60.0 (minor) fix(deps): update sentry packages to v7.60.1 (minor) Jul 26, 2023
@renovate renovate bot force-pushed the renovate/sentry-packages branch from d81aa07 to 35854a1 Compare July 26, 2023 16:59
@renovate renovate bot changed the title fix(deps): update sentry packages to v7.60.1 (minor) fix(deps): update sentry packages to v7.61.0 (minor) Jul 31, 2023
@renovate renovate bot force-pushed the renovate/sentry-packages branch from 35854a1 to 4c03b18 Compare July 31, 2023 16:18
@spaenleh spaenleh merged commit 9cd0410 into main Aug 1, 2023
2 checks passed
@renovate renovate bot deleted the renovate/sentry-packages branch August 1, 2023 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file v1.0.3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant