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

Deps: Bump @sentry/react from 7.57.0 to 7.68.0 #3860

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 8, 2023

Bumps @sentry/react from 7.57.0 to 7.68.0.

Release notes

Sourced from @​sentry/react's releases.

7.68.0

  • feat(browser): Add BroadcastChannel and SharedWorker to TryCatch EventTargets (#8943)
  • feat(core): Add name to Span (#8949)
  • feat(core): Add ServerRuntimeClient (#8930)
  • fix(node-experimental): Ensure span.finish() works as expected (#8947)
  • fix(remix): Add new sourcemap-upload script files to prepack assets. (#8948)
  • fix(publish): Publish downleveled TS3.8 types and fix types path (#8954)

Bundle size 📦

Path Size
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped) 75.35 KB
@​sentry/browser (incl. Tracing) - Webpack (gzipped) 31.24 KB
@​sentry/browser - Webpack (gzipped) 21.84 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped) 69.87 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped) 28.18 KB
@​sentry/browser - ES6 CDN Bundle (gzipped) 20.18 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed) 220.81 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed) 85.09 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed) 59.73 KB
@​sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped) 31.08 KB
@​sentry/react (incl. Tracing, Replay) - Webpack (gzipped) 75.37 KB
@​sentry/react - Webpack (gzipped) 21.88 KB
@​sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped) 93.23 KB
@​sentry/nextjs Client - Webpack (gzipped) 50.81 KB

7.67.0

Important Changes

  • feat: Mark errors caught by the SDK as unhandled
    • feat(browser): Mark errors caught from TryCatch integration as unhandled (#8890)
    • feat(integrations): Mark errors caught from HttpClient and CaptureConsole integrations as unhandled (#8891)
    • feat(nextjs): Mark errors caught from NextJS wrappers as unhandled (#8893)
    • feat(react): Mark errors captured from ErrorBoundary as unhandled (#8914)
    • feat(remix): Mark errors caught from Remix instrumentation as unhandled (#8894)
    • feat(serverless): Mark errors caught in Serverless handlers as unhandled (#8907)
    • feat(vue): Mark errors caught by Vue wrappers as unhandled (#8905)

This release fixes inconsistent behaviour of when our SDKs classify captured errors as unhandled. Previously, some of our instrumentations correctly set unhandled, while others set handled. Going forward, all errors caught automatically from our SDKs will be marked as unhandled. If you manually capture errors (e.g. by calling Sentry.captureException), your errors will continue to be reported as handled.

This change might lead to a decrease in reported crash-free sessions and consequently in your release health score. If you have concerns about this, feel free to open an issue.

Other Changes

  • feat(node-experimental): Implement new performance APIs (#8911)

... (truncated)

Changelog

Sourced from @​sentry/react's changelog.

7.68.0

  • feat(browser): Add BroadcastChannel and SharedWorker to TryCatch EventTargets (#8943)
  • feat(core): Add name to Span (#8949)
  • feat(core): Add ServerRuntimeClient (#8930)
  • fix(node-experimental): Ensure span.finish() works as expected (#8947)
  • fix(remix): Add new sourcemap-upload script files to prepack assets. (#8948)
  • fix(publish): Publish downleveled TS3.8 types and fix types path (#8954)

7.67.0

Important Changes

  • feat: Mark errors caught by the SDK as unhandled
    • feat(browser): Mark errors caught from TryCatch integration as unhandled (#8890)
    • feat(integrations): Mark errors caught from HttpClient and CaptureConsole integrations as unhandled (#8891)
    • feat(nextjs): Mark errors caught from NextJS wrappers as unhandled (#8893)
    • feat(react): Mark errors captured from ErrorBoundary as unhandled (#8914)
    • feat(remix): Add debugid injection and map deletion to sourcemaps script (#8814)
    • feat(remix): Mark errors caught from Remix instrumentation as unhandled (#8894)
    • feat(serverless): Mark errors caught in Serverless handlers as unhandled (#8907)
    • feat(vue): Mark errors caught by Vue wrappers as unhandled (#8905)

This release fixes inconsistent behaviour of when our SDKs classify captured errors as unhandled. Previously, some of our instrumentations correctly set unhandled, while others set handled. Going forward, all errors caught automatically from our SDKs will be marked as unhandled. If you manually capture errors (e.g. by calling Sentry.captureException), your errors will continue to be reported as handled.

This change might lead to a decrease in reported crash-free sessions and consequently in your release health score. If you have concerns about this, feel free to open an issue.

Other Changes

  • feat(node-experimental): Implement new performance APIs (#8911)
  • feat(node-experimental): Sync OTEL context with Sentry AsyncContext (#8797)
  • feat(replay): Allow to configure maxReplayDuration (#8769)
  • fix(browser): Add replay and profiling options to BrowserClientOptions (#8921)
  • fix(browser): Check for existence of instrumentation targets (#8939)
  • fix(nextjs): Don't re-export default in route handlers (#8924)
  • fix(node): Improve mysql integration (#8923)
  • fix(remix): Guard against missing default export for server instrument (#8909)
  • ref(browser): Deprecate top-level wrap function (#8927)
  • ref(node-otel): Avoid exporting internals & refactor attribute adding (#8920)

Work in this release contributed by @​SorsOps. Thank you for your contribution!

7.66.0

  • fix: Defer tracing decision to downstream SDKs when using SDK without performance (#8839)
  • fix(nextjs): Fix package.json exports (#8895)

... (truncated)

Commits
  • d074cec release: 7.68.0
  • 86badae Merge pull request #8958 from getsentry/prepare-release/7.68.0
  • 5dd16de meta: Update Changelog for 7.68.0
  • 8766bdd fix(ts): Publish downleveled TS3.8 types, fix types path (#8954)
  • 6643671 feat(core): Add name to Span (#8949)
  • 0d49557 fix(node-experimental): Ensure span.finish() works as expected (#8947)
  • 3487fa3 fix(remix): Add new sourcemap-upload script files to prepack assets. (#8948)
  • f54e121 feat(core): Add ServerRuntimeClient (#8930)
  • e2f0f4b docs(node-experimental): Update readme for current status (#8945)
  • 1e8921b feat(browser): Add BroadcastChannel and SharedWorker to TryCatch EventTar...
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

@dependabot dependabot bot requested a review from a team as a code owner September 8, 2023 13:50
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Sep 8, 2023
@github-actions
Copy link

github-actions bot commented Sep 8, 2023

Conventional Commits Report

Type Number
Dependencies 1

🚀 Conventional commits found.

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/main/sentry/react-7.68.0 branch from 09c849d to be5e233 Compare September 11, 2023 11:39
Bumps [@sentry/react](https://github.com/getsentry/sentry-javascript) from 7.57.0 to 7.68.0.
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md)
- [Commits](getsentry/sentry-javascript@7.57.0...7.68.0)

---
updated-dependencies:
- dependency-name: "@sentry/react"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/main/sentry/react-7.68.0 branch from be5e233 to 14a31bd Compare September 11, 2023 12:00
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Sep 22, 2023

Superseded by #3874.

@dependabot dependabot bot closed this Sep 22, 2023
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/main/sentry/react-7.68.0 branch September 22, 2023 14:21
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 javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants