Skip to content

Bump @sentry/nextjs from 7.110.1 to 8.1.0

DependabotCatalogueIndicateurs requested to merge dependabot-npm_and_yarn-sentry-nextjs-8.1.0 into develop

Bumps @sentry/nextjs from 7.110.1 to 8.1.0.

Release notes

Sourced from @​sentry/nextjs's releases.

8.1.0

This release mainly fixes a couple of bugs from the initial 8.0.0 release. In addition to the changes below, we updated some initially missed points in our migration guides and documentation.

  • feat(aws-serverless): Fix tree-shaking for aws-serverless package (#12017)
  • feat(node): Bump opentelemetry instrumentation to latest version (#12028)
  • feat(scope): Bring back lastEventId on isolation scope (#11951) (#12022)
  • fix(aws-serverless): Export awslambda-auto
  • fix(node): Do not warn for missing instrumentation if SDK is disabled (#12041)
  • fix(react): Set dependency-injected functions as early as possible (#12019)
  • fix(react): Warn and fall back gracefully if dependency injected functions are not available (#12026)
  • ref(core): Streamline parseSampleRate utility function (#12024)
  • ref(feedback): Make eventId optional and use lastEventId in report dialog (#12029)

8.0.0

The Sentry JS SDK team is proud to announce the release of version 8.0.0 of Sentry's JavaScript SDKs - it's been a long time coming! Thanks to everyone for your patience and a special shout out to the brave souls testing preview builds and reporting issues - we appreciate your support!

How to Upgrade to Version 8:

We recommend reading the migration guide docs to find out how to address any breaking changes in your code for your specific platform or framework.

To automate upgrading to v8 as much as possible, use our migration codemod @sentry/migr8:

npx @sentry/migr8@latest

All deprecations from the v7 cycle, with the exception of getCurrentHub(), have been removed and can no longer be used in v8. If you have an advanced Sentry SDK setup, we additionally recommend reading the in-depth migration guide in our repo which highlights all changes with additional details and information.

The rest of this changelog highlights the most important (breaking) changes and links to more detailed information.

Version Support

With v8, we dropped support for several old runtimes and browsers

Node SDKs: The Sentry JavaScript SDK v8 now supports Node.js 14.8.0 or higher. This applies to @sentry/node and all of our node-based server-side sdks (@sentry/nextjs, @sentry/remix, etc.). Furthermore, version 8 now ships with full support for ESM-based node apps using Node.js 18.19.0 or higher.

Browser SDKs: The browser SDKs now require ES2018+

... (truncated)

Changelog

Sourced from @​sentry/nextjs's changelog.

8.1.0

This release mainly fixes a couple of bugs from the initial 8.0.0 release. In addition to the changes below, we updated some initially missed points in our migration guides and documentation.

  • feat(aws-serverless): Fix tree-shaking for aws-serverless package (#12017)
  • feat(node): Bump opentelemetry instrumentation to latest version (#12028)
  • feat(scope): Bring back lastEventId on isolation scope (#11951) (#12022)
  • fix(aws-serverless): Export awslambda-auto
  • fix(node): Do not warn for missing instrumentation if SDK is disabled (#12041)
  • fix(react): Set dependency-injected functions as early as possible (#12019)
  • fix(react): Warn and fall back gracefully if dependency injected functions are not available (#12026)
  • ref(core): Streamline parseSampleRate utility function (#12024)
  • ref(feedback): Make eventId optional and use lastEventId in report dialog (#12029)

8.0.0

The Sentry JS SDK team is proud to announce the release of version 8.0.0 of Sentry's JavaScript SDKs - it's been a long time coming! Thanks to everyone for your patience and a special shout out to the brave souls testing preview builds and reporting issues - we appreciate your support!

How to Upgrade to Version 8:

We recommend reading the migration guide docs to find out how to address any breaking changes in your code for your specific platform or framework.

To automate upgrading to v8 as much as possible, use our migration codemod @sentry/migr8:

npx @sentry/migr8@latest

All deprecations from the v7 cycle, with the exception of getCurrentHub(), have been removed and can no longer be used in v8. If you have an advanced Sentry SDK setup, we additionally recommend reading the in-depth migration guide in our repo which highlights all changes with additional details and information.

The rest of this changelog highlights the most important (breaking) changes and links to more detailed information.

Version Support

With v8, we dropped support for several old runtimes and browsers

Node SDKs: The Sentry JavaScript SDK v8 now supports Node.js 14.8.0 or higher. This applies to @sentry/node and all of our node-based server-side sdks (@sentry/nextjs, @sentry/remix, etc.). Furthermore, version 8 now ships with full support for ESM-based node apps using Node.js 18.19.0 or higher.

... (truncated)

Commits
  • d31d7a0 release: 8.1.0
  • b135be6 Merge pull request #12062 from getsentry/prepare-release/8.1.0
  • fddbe2a meta: Update CHANGELOG for 8.1.0
  • ef26423 revert: "feat(browser): Add interactionsSampleRate to `browserTracingIntegr...
  • 32bf90c fix(docs): Reorder how to determine version numbers for releases (#12050)
  • 42e9b23 test(e2e): Enable ESM loader test (#12020)
  • 13b1897 test(e2e): Update node version used for e2e tests (#12031)
  • 733ae1d fix(node): Do not warn for missing instrumentation if SDK is disabled (#12041)
  • d5568d8 ref(feedback): Make eventId optional and use lastEventId in report dialog...
  • 6f81262 feat(scope): Bring back lastEventId on isolation scope (#11951) (#12022)
  • Additional commits viewable in compare view

Merge request reports