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

Update sentry-javascript monorepo to v7.31.1 #454

Merged
merged 1 commit into from
Jan 19, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 14, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

getsentry/sentry-javascript

v7.31.1

Compare Source

  • build(replay): Provide full browser+tracing+replay bundle (#​6793)
  • feat(nextjs): Disable NextJS perf monitoring when using otel (#​6820)
  • fix(nextjs): Add back browser field in package.json (#​6809)
  • fix(nextjs): Connect Edge API route errors to span (#​6806)
  • fix(nextjs): Correctly handle ts middleware files (#​6816)

v7.31.0

Compare Source

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)

v7.30.0

Compare Source

  • 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!


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 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 force-pushed the renovate/sentry-javascript-monorepo branch 4 times, most recently from 2b1ce89 to 1033720 Compare January 16, 2023 18:03
@renovate renovate bot changed the title Update sentry-javascript monorepo to v7.30.0 Update sentry-javascript monorepo to v7.31.0 Jan 16, 2023
@renovate renovate bot force-pushed the renovate/sentry-javascript-monorepo branch from 1033720 to a75b14a Compare January 16, 2023 23:33
@renovate renovate bot force-pushed the renovate/sentry-javascript-monorepo branch from a75b14a to 066531e Compare January 17, 2023 20:53
@renovate renovate bot changed the title Update sentry-javascript monorepo to v7.31.0 Update sentry-javascript monorepo to v7.31.1 Jan 17, 2023
@ranger-ross ranger-ross merged commit 96429db into main Jan 19, 2023
@ranger-ross ranger-ross deleted the renovate/sentry-javascript-monorepo branch January 19, 2023 11:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant