search

gliff-ai / dominate

gliff.ai DOMINATE – a frontend platform that combines together all gliff.ai products and end-to-end encryption storage with the database models for use
https://staging.gliff.app
Other
0 stars 0 forks source link

build(deps): bump @sentry/react from 6.19.7 to 7.11.1 #820

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps @sentry/react from 6.19.7 to 7.11.1.

Release notes

Sourced from @​sentry/react's releases.

7.11.1

  • fix(remix): Store transaction on express req (#5595)

7.11.0

This release introduces updates the tracingOrigins option to not attach any headers/create an spans when supplied with an empty array ([]). Previously, we would supply the default tracingOrigins if an empty array was set as the tracingOrigins option.

  • fix(core): Suppress stack when SentryError isn't an error (#5562)
  • feat(nextjs): Wrap server-side getInitialProps (#5546)
  • feat(nextjs): Improve pageload transaction creation (#5574)
  • feat(nextjs): Add spans and route parameterization in data fetching wrappers (#5564)
  • feat(nextjs): Create spans and route parameterization in server-side getInitialProps (#5587)
  • fix(remix): Use domains to prevent scope bleed (#5570)
  • fix(remix): Wrap domains properly on instrumentServer (#5590)
  • feat(remix): Add route ID to remix routes (#5568)
  • feat(remix): Export a manual wrapper for custom Express servers (#5524)
  • feat(tracing): Add long task collection (#5529)
  • feat(tracing): Allow for setting of an empty array (#5583)

7.10.0

This release introduces the first alpha version of @sentry/svelte, our newest JavaScript SDK! For details on how to use it, please see the README and the tracking GitHub issue.

  • feat(react): Track duration of React component updates (#5531)
  • feat(svelte): Add Error and Performance Instrumentation from Browser SDK (#5543)
  • feat(svelte): Add Svelte SDK Package Boilerplate (#5535)
  • fix(integration): Don't mangle localforage internals (#5534)
  • fix(react): Set redux state context properly (#5550)
  • fix(remix): Support merging json responses from root loader functions. (#5548)
  • fix(remix): Return response if detected in root loader (#5558)
  • ref(nextjs): Move autoWrapDataFetchers option into experiments object (#5540)
  • ref(nextjs): Wrap server-side data-fetching methods during build (#5503)

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

7.9.0

This release adds the tracePropagationTargets option to the Sentry Node SDK.

  • feat(node): Add tracePropagationTargets option (#5521)
  • fix(browser): Parse Chrome stack frames without full paths (#5519)
  • fix(browser): Set : as a part of gecko protocol regex group. (#4153)
  • fix(browser): Strip webpack wrapping from stack frames (#5522)
  • fix(nextjs): Pull transpileClientSDK option from correct location (#5516)
  • fix(node): Handle colons in stack trace paths (#5517)
  • fix(react): Fix React Router v6 paramaterization (#5515)
  • fix(remix): Paramaterize server side transactions (#5491)
  • fix(remix): Provide sentry-trace and baggage via root loader. (#5509)
  • ref(nextjs): Prework for wrapping data-fetching functions (#5508)
  • ref(nextjs): Simplify NextConfigObject type (#5514)

7.8.1

  • fix(nextjs): Add default distDir value back into index.server.ts (#5479)

... (truncated)

Changelog

Sourced from @​sentry/react's changelog.

7.11.1

  • fix(remix): Store transaction on express req (#5595)

7.11.0

This release introduces updates the tracingOrigins option to not attach any headers/create an spans when supplied with an empty array ([]). Previously, we would supply the default tracingOrigins if an empty array was set as the tracingOrigins option.

  • fix(core): Suppress stack when SentryError isn't an error (#5562)
  • feat(nextjs): Wrap server-side getInitialProps (#5546)
  • feat(nextjs): Improve pageload transaction creation (#5574)
  • feat(nextjs): Add spans and route parameterization in data fetching wrappers (#5564)
  • feat(nextjs): Create spans and route parameterization in server-side getInitialProps (#5587)
  • fix(remix): Use domains to prevent scope bleed (#5570)
  • fix(remix): Wrap domains properly on instrumentServer (#5590)
  • feat(remix): Add route ID to remix routes (#5568)
  • feat(remix): Export a manual wrapper for custom Express servers (#5524)
  • feat(tracing): Add long task collection (#5529)
  • feat(tracing): Allow for setting of an empty array (#5583)

7.10.0

This release introduces the first alpha version of @sentry/svelte, our newest JavaScript SDK! For details on how to use it, please see the README and the tracking GitHub issue.

  • feat(react): Track duration of React component updates (#5531)
  • feat(svelte): Add Error and Performance Instrumentation from Browser SDK (#5543)
  • feat(svelte): Add Svelte SDK Package Boilerplate (#5535)
  • fix(integration): Don't mangle localforage internals (#5534)
  • fix(react): Set redux state context properly (#5550)
  • fix(remix): Support merging json responses from root loader functions. (#5548)
  • fix(remix): Return response if detected in root loader (#5558)
  • ref(nextjs): Move autoWrapDataFetchers option into experiments object (#5540)
  • ref(nextjs): Wrap server-side data-fetching methods during build (#5503)

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

7.9.0

This release adds the tracePropagationTargets option to the Sentry Node SDK.

  • feat(node): Add tracePropagationTargets option (#5521)
  • fix(browser): Parse Chrome stack frames without full paths (#5519)
  • fix(browser): Set : as a part of gecko protocol regex group. (#4153)
  • fix(browser): Strip webpack wrapping from stack frames (#5522)
  • fix(nextjs): Pull transpileClientSDK option from correct location (#5516)
  • fix(node): Handle colons in stack trace paths (#5517)
  • fix(react): Fix React Router v6 paramaterization (#5515)
  • fix(remix): Paramaterize server side transactions (#5491)
  • fix(remix): Provide sentry-trace and baggage via root loader. (#5509)
  • ref(nextjs): Prework for wrapping data-fetching functions (#5508)

... (truncated)

Commits
  • c9d76df release: 7.11.1
  • a1fd7c4 meta: 7.11.1 CHANGELOG (#5597)
  • 8e21f0d fix(remix): Store transaction on express req (#5595)
  • 8c58e0d Merge branch 'release/7.11.0'
  • 753ad86 release: 7.11.0
  • 2306940 meta: Update CHANGELOG for 7.11.0 (#5588)
  • 2f6deeb feat(nextjs): Create spans and route parameterization in server-side `getInit...
  • e861cc4 feat(nextjs): Add spans and route parameterization in data fetching wrappers ...
  • c2cdf92 fix(remix): Wrap domains properly on instrumentServer (#5590)
  • bdd7fde fix(remix): Use domains to prevent scope bleed (#5570)
  • 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 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[bot] commented 2 years ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.