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.31.0 #1004

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps @sentry/browser from 6.11.0 to 7.31.0.

Release notes

Sourced from @​sentry/browser's releases.

7.30.0

  • feat(core): Add addIntegration method to client (#6651)
  • feat(core): Add replay_event type for events (#6481)
  • feat(gatsby): Support Gatsby v5 (#6635)
  • feat(integrations): Add HTTPClient integration (#6500)
  • feat(node): Add LocalVariables integration to capture local variables to stack frames (#6478)
  • feat(node): Check for invalid url in node transport (#6623)
  • feat(replay): Remove replayType from tags and into replay_event (#6658)
  • feat(transport): Return result through Transport send (#6626)
  • fix(nextjs): Don't wrap res.json and res.send (#6674)
  • fix(nextjs): Don't write to res.end to fix next export (#6682)
  • fix(nextjs): Exclude SDK from Edge runtime bundles (#6683)
  • fix(replay): Allow Replay to be used in Electron renderers with nodeIntegration enabled (#6644)
  • fix(utils): Ignore stack frames over 1kb (#6627)
  • ref(angular) Add error-like objects handling (#6446)
  • ref(nextjs): Remove instrumentSever (#6592)

Work in this release contributed by @​rjoonas, @​Naddiseo, and @​theofidry. Thank you for your contributions!

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)

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

7.31.0

The Next.js SDK now supports error and performance monitoring for Next.js middleware and Edge API routes. To set it up, add a sentry.edge.config.js or sentry.edge.config.ts file to the root of your project and initialize the SDK:

// sentry.edge.config.js or sentry.edge.config.ts

import * as Sentry from "@​sentry/nextjs";


const SENTRY_DSN = process.env.SENTRY_DSN || process.env.NEXT_PUBLIC_SENTRY_DSN;


Sentry.init({
dsn: SENTRY_DSN || "YOUR DSN HERE",
tracesSampleRate: 1.0,
});

The Next.js will automatically instrument Edge API routes and middleware. If you want to opt out of automatic instrumentation of middleware can use the autoInstrumentMiddleware option in the sentry object of your Next.js configuration:

const moduleExports = {
  sentry: {
    autoInstrumentMiddleware: false,
  },
};

Middleware can be manually instrumented by using the wrapMiddlewareWithSentry function.

  • feat(nextjs): Add Edge Runtime SDK (#6752)
  • feat(nextjs): Add optional options argument to withSentryConfig as an alternative to the sentry property (#6721)
  • feat(nextjs): Add edge route and middleware wrappers (#6771)
  • feat(nextjs): Auto-wrap edge-routes and middleware (#6746)
  • feat(replay): Update rrweb & rrweb-snapshot (#6749)
  • feat(replay): Stop recording when retry fails (#6765)
  • feat(replay): Stop without retry when receiving bad API response (#6773)
  • feat(types): Add Trace Context type (#6714)
  • fix(nextjs): Export isomorphic data fetching wrappers from client SDK (#6790)
  • fix(nextjs): Make Next.js types isomorphic (#6707)
  • fix(node): Handle node build without inspector in LocalVariables integration (#6780)
  • fix(otel): Set trace context via Otel Span instead of Sentry span (#6724)
  • fix(otel): Prevent baggage from being overwritten (#6709)
  • fix(otel): Make sure we handle when sentry-trace is an empty array (#6781)
  • fix(remix): Make remix SDK type exports isomorphic (#6715)
  • fix(replay): Fix checkoutEveryNms (#6722)
  • fix(replay): Fix incorrect uncompressed recording size due to encoding (#6740)
  • fix(tracing): Attach request instrumentation span to active span instead of current transaction (#6778)
  • ref(nextjs): Deprecate isBuild() and IS_BUILD (#6727)

... (truncated)

Commits
  • ead59ad release: 7.31.0
  • 38f49ca meta: CHANGELOG for 7.31.0 (#6787)
  • f29f4b1 fix(nextjs): Export isomorphic data fetching wrappers from client SDK (#6790)
  • 28a430d ref(nextjs): Rename wrapper functions (#6788)
  • aed2ce6 fix(replay): Fix incorrect uncompressed recording size due to encoding (#6740)
  • 4365c66 chore: Add flaky test template (#6786)
  • 06b3455 fix(node): Handle node build without inspector in LocalVariables integrat...
  • 81ef0ca feat(replay): Stop without retry when receiving bad API response (#6773)
  • 1e72c0c ci(replay): Overhead measurement (#6611)
  • ed136de fix(tracing): Attach request instrumentation span to active span instead of c...
  • 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 #1005.