search

bitwave-tv / bitwave

Front end for [bitwave.tv] - an open platform live video streaming service
https://bitwave.tv
GNU General Public License v3.0
142 stars 32 forks source link

Bump @sentry/browser from 6.11.0 to 7.29.0 #998

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps @sentry/browser from 6.11.0 to 7.29.0.

Release notes

Sourced from @​sentry/browser's releases.

7.29.0

This update includes a change to the @sentry/nextjs SDK that may increase response times of requests in applications deployed to Vercel or AWS lambdas to ensure that error events are sent consistently. Additionally, Next.js applications deployed to Vercel or AWS lambdas may also see an uptick in sent transactions. (for more information see #6578)

  • feat(core): Add getSdkMetadata to Client (#6643)
  • feat(nextjs): Send events consistently on platforms that don't support streaming (#6578)
  • feat(replay): Use new prepareEvent util & ensure dropping replays works (#6522)
  • feat(types): Upstream some replay types (#6506)
  • fix(replay): Envelope send should be awaited in try/catch (#6625)
  • fix(replay): Improve handling of maskAllText selector (#6637)
  • fix(tracing): Don't finish React Router 6 pageload transactions early (#6609)

7.28.1

  • fix(replay): Do not mangle _metadata in client options (#6600)
  • fix(replay): Cater for event processor returning null (#6576)

7.28.0

  • feat(nextjs): Check for Vercel Edge Function GA (#6565)
  • feat(utils): Improved envelope parser (#6580)
  • fix(nextjs): Export Replay from index.server.ts to avoid TS error (#6577)
  • fix(nextjs): Pass this through wrappers (#6572)
  • ref(types): Add undefined as possible event type (#6584)

7.27.0

This release exports the Session Replay integration via @sentry/browser and all framework SDKs building on top of it. Going forward, the @sentry/replay package doesn't have to be installed explicitly to use Replay. Furthermore, this release increases the maximim replay session duration from 30 minutes to 1 hour.

  • feat(browser): Export Replay integration from Browser SDK (#6508)
  • feat(replay): Change MAX_SESSION_LIFE to 1 hour (#6561)
  • feat(replay): Do not capture errors originating from rrweb (#6521)
  • feat(replay): Flush immediately on DOM checkouts (#6463)
  • fix(core): Make beforeSend handling defensive for different event types (#6507)
  • fix(replay): Ensure lodash.debounce does not trigger next.js warning (#6551)
  • fix(replay): Make maskAllText selector more specific (#6544)
  • fix(replay): Send dsn in envelope header if tunneling is active (#6568)
  • fix(utils): Don't attach context lines to stack frames without line number (#6549)
  • ref(replay): Send SDK's name in replay event (#6514)

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

7.26.0

  • feat(browser): Export event builder methods for use in other SDKs (#6515)
  • feat(types): Add threads to Event (#6516)
  • feat(nextjs): Add option to automatically tunnel events (#6425)
  • fix(nextjs): Fix automatic release value discovery (#6513)
  • ref(nextjs): Use generic loader to inject global values (#6484)

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

7.29.0

This update includes a change to the @sentry/nextjs SDK that may increase response times of requests in applications deployed to Vercel or AWS lambdas to ensure that error events are sent consistently. Additionally, Next.js applications deployed to Vercel or AWS lambdas may also see an uptick in sent transactions. (for more information see #6578)

  • feat(core): Add getSdkMetadata to Client (#6643)
  • feat(nextjs): Send events consistently on platforms that don't support streaming (#6578)
  • feat(replay): Use new prepareEvent util & ensure dropping replays works (#6522)
  • feat(types): Upstream some replay types (#6506)
  • fix(replay): Envelope send should be awaited in try/catch (#6625)
  • fix(replay): Improve handling of maskAllText selector (#6637)
  • fix(tracing): Don't finish React Router 6 pageload transactions early (#6609)

7.28.1

  • fix(replay): Do not mangle _metadata in client options (#6600)
  • fix(replay): Cater for event processor returning null (#6576)

7.28.0

  • feat(nextjs): Check for Vercel Edge Function GA (#6565)
  • feat(utils): Improved envelope parser (#6580)
  • fix(nextjs): Export Replay from index.server.ts to avoid TS error (#6577)
  • fix(nextjs): Pass this through wrappers (#6572)
  • ref(types): Add undefined as possible event type (#6584)

7.27.0

This release exports the Session Replay integration via @sentry/browser and all framework SDKs building on top of it. Going forward, the @sentry/replay package doesn't have to be installed explicitly to use Replay. Furthermore, this release increases the maximim replay session duration from 30 minutes to 1 hour.

  • feat(browser): Export Replay integration from Browser SDK (#6508)
  • feat(replay): Change MAX_SESSION_LIFE to 1 hour (#6561)
  • feat(replay): Do not capture errors originating from rrweb (#6521)
  • feat(replay): Flush immediately on DOM checkouts (#6463)
  • fix(core): Make beforeSend handling defensive for different event types (#6507)
  • fix(replay): Ensure lodash.debounce does not trigger next.js warning (#6551)
  • fix(replay): Make maskAllText selector more specific (#6544)
  • fix(replay): Send dsn in envelope header if tunneling is active (#6568)
  • fix(utils): Don't attach context lines to stack frames without line number (#6549)
  • ref(replay): Send SDK's name in replay event (#6514)

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

7.26.0

  • feat(browser): Export event builder methods for use in other SDKs (#6515)

... (truncated)

Commits
  • a06f95e release: 7.29.0
  • d1934af meta: Update changelog for 7.29.0 (#6652)
  • c157f86 feat(core): Add getSdkMetadata to Client (#6643)
  • b03a32b ref(replay): Extract flush min and max delay default values to constants (#6612)
  • b674c26 feat(replay): Use new prepareEvent util & ensure dropping replays works (#6...
  • 65cd080 fix(tracing): Don't finish React Router 6 pageload transactions early (#6609)
  • 23a7d0b ref(replay): Replace lodash.debounce with custom debounce implementation (#...
  • 371d42d feat(nextjs): Send events consistently on platforms that don't support stream...
  • 3b1bcaf fix(replay): Improve handling of maskAllText selector (#6637)
  • a23bda5 feat(types): Upstream some replay types (#6506)
  • 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 1 year ago

Superseded by #1002.