Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 51 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,57 @@

- "You miss 100 percent of the chances you don't take. — Wayne Gretzky" — Michael Scott

## 7.31.0

The Next.js SDK now supports error and performance monitoring for Next.js [middleware](https://nextjs.org/docs/advanced-features/middleware) and [Edge API routes](https://nextjs.org/docs/api-routes/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:

```js
// 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:

```javascript
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)

## 7.30.0

- feat(core): Add `addIntegration` method to client (#6651)
Expand Down
27 changes: 21 additions & 6 deletions MIGRATION.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,33 @@
# Deprecations in 7.x
# Deprecations in 7.x

## Deprecated `tracingOrigins` (since 7.19.0) - #6176
## Renaming of Next.js wrapper methods (since 7.31.0) - #6790

The `tracingOrigins` option is deprecated in favor of using `shouldCreateSpanForRequest` and `tracePropagationTargets`.
We updated the names of the functions to wrap data fetchers and API routes to better reflect what they are doing.
The old methods can still be used but are deprecated and will be removed in the next major update of the SDK.

## Deprecate `componentTrackingPreprocessor` in Svelte SDK (since 7.16.0) - #5936
Following function names were updated:

This release adds the `withSentryConfig` feature to the Svelte SDK. It replaces the now deprecated Svelte `componentTrackingPreprocessor` which will be removed in the next major release.
- `withSentryAPI` was renamed to `wrapApiHandlerWithSentry`
- `withSentryGetServerSideProps` was renamed to `wrapGetServerSidePropsWithSentry`
- `withSentryGetStaticProps` was renamed to `wrapGetStaticPropsWithSentry`
- `withSentryServerSideGetInitialProps` was renamed to `wrapGetInitialPropsWithSentry`
- `withSentryServerSideAppGetInitialProps` was renamed to `wrapAppGetInitialPropsWithSentry`
- `withSentryServerSideDocumentGetInitialProps` was renamed to `wrapDocumentGetInitialPropsWithSentry`
- `withSentryServerSideErrorGetInitialProps` was renamed to `wrapErrorGetInitialPropsWithSentry`

## Deprecated `tracingOrigins` (since 7.19.0) - #6176

The `tracingOrigins` option is deprecated in favor of using `shouldCreateSpanForRequest` and `tracePropagationTargets`.

## Deprecate `componentTrackingPreprocessor` in Svelte SDK (since 7.16.0) - #5936

This release adds the `withSentryConfig` feature to the Svelte SDK. It replaces the now deprecated Svelte `componentTrackingPreprocessor` which will be removed in the next major release.

## Deprecate `getGlobalObject` in `@sentry/utils` (since 7.16.0) - #5949

This is no longer used.

## Deprecate @sentry/hub (since 7.15.0) - #5823
## Deprecate @sentry/hub (since 7.15.0) - #5823

This release deprecates `@sentry/hub` and all of it's exports. All of the `@sentry/hub` exports have moved to `@sentry/core`. `@sentry/hub` will be removed in the next major release.

Expand Down