Skip to content

Bump @nuxtjs/sentry from 4.0.0 to 6.0.0 in /webapp

Created by: dependabot[bot]

Bumps @nuxtjs/sentry from 4.0.0 to 6.0.0.

Release notes

Sourced from @​nuxtjs/sentry's releases.

6.0.0

BREAKING CHANGES

  • The server-side process.sentry will be created slightly later than before WHEN running the "build" action. It will be created before the pages are built (on build:compile hook) while before it was available a bit earlier on ready hook (with an issue that it was not always able to pass the project version to Sentry).
  • options: Remove deprecated webpackConfig option. Configure through the publishRelease option instead.
  • options: Remove deprecated attachCommits and repo options. Those can now be set through the publishRelease option.
  • deps: Don't ship with @sentry/webpack-plugin as a dependency. To use the "publishRelease" option, it's now necessary to manually install that package as a dev dependency.

Features

  • support for registering external integrations (#276) (2cf56ef)

Bug Fixes

  • deps: update devdependency @​sentry/webpack-plugin to ^1.19.0 (#434) (694ba04)
  • deps: update sentry dependencies (#405) (a465f39)
  • throw error instead of logging when @​sentry/webpack-plugin missing (d437a37)
  • use different hook for initializing server-side Sentry instance (#403) (20734fa)
  • deps: Don't ship with @sentry/webpack-plugin as a dependency (#390) (b042a46)
  • deps: update dependency @​sentry/webpack-plugin to ^1.18.7 (#392) (f72147f)
  • deps: update sentry dependencies (#388) (5251cb6)
  • deps: update sentry dependencies (#396) (7fec526)

Code Refactoring

  • options: remove deprecated "attachCommits" and "repo" (#393) (1efcd28)
  • options: remove deprecated "webpackConfig" (#394) (859101e)

6.0.0-beta.4

BREAKING CHANGES

  • The server-side process.sentry will be created slightly later than before WHEN running the "build" action. It will be created before the pages are built (on build:compile hook) while before it was available a bit earlier on ready hook (with an issue that it was not always able to pass the project version to Sentry).
  • options: Remove deprecated webpackConfig option. Configure through the publishRelease option instead.
  • options: Remove deprecated attachCommits and repo options. Those can now be set through the publishRelease option.
  • deps: Don't ship with @sentry/webpack-plugin as a dependency. To use the "publishRelease" option, it's now necessary to manually install that package as a dev dependency.

Features

  • support for registering external integrations (#276) (2cf56ef)

Bug Fixes

  • deps: Don't ship with @sentry/webpack-plugin as a dependency (#390) (b042a46)
  • deps: update devdependency @​sentry/webpack-plugin to ^1.19.0 (#434) (694ba04)
  • deps: update sentry dependencies (#396) (7fec526)

... (truncated)

Changelog

Sourced from @​nuxtjs/sentry's changelog.

6.0.0 (2022-08-26)

BREAKING CHANGES

  • The server-side process.sentry will be created slightly later than before WHEN running the "build" action. It will be created before the pages are built (on build:compile hook) while before it was available a bit earlier on ready hook (with an issue that it was not always able to pass the project version to Sentry).
  • options: Remove deprecated webpackConfig option. Configure through the publishRelease option instead.
  • options: Remove deprecated attachCommits and repo options. Those can now be set through the publishRelease option.
  • deps: Don't ship with @sentry/webpack-plugin as a dependency. To use the "publishRelease" option, it's now necessary to manually install that package as a dev dependency.

Features

  • support for registering external integrations (#276) (2cf56ef)

Bug Fixes

  • deps: update devdependency @​sentry/webpack-plugin to ^1.19.0 (#434) (694ba04)
  • deps: update sentry dependencies (#405) (a465f39)
  • throw error instead of logging when @​sentry/webpack-plugin missing (d437a37)
  • use different hook for initializing server-side Sentry instance (#403) (20734fa)
  • deps: Don't ship with @sentry/webpack-plugin as a dependency (#390) (b042a46)
  • deps: update dependency @​sentry/webpack-plugin to ^1.18.7 (#392) (f72147f)
  • deps: update sentry dependencies (#388) (5251cb6)
  • deps: update sentry dependencies (#396) (7fec526)

Code Refactoring

  • options: remove deprecated "attachCommits" and "repo" (#393) (1efcd28)
  • options: remove deprecated "webpackConfig" (#394) (859101e)

5.1.7 (2022-02-02)

Bug Fixes

  • deps: update sentry dependencies (#379) (e7db004)
  • don't pass empty object to integrations constructor (#387) (b4b9415)

5.1.6 (2021-11-26)

Bug Fixes

  • deps: update sentry dependencies to ^6.14.3 (#367) (7a38d27)
  • deps: update sentry dependencies to ^6.15.0 (#374) (77fcf74)
  • don't pass empty object to integrations constructor (#376) (18e12c5)

5.1.5 (2021-11-05)

... (truncated)

Commits
  • a7d9470 chore: release 6.0.0
  • 5c87071 chore(ci): switch to main branch
  • dff537c chore(deps): update devdependency sentry-testkit to v4 (#436)
  • 136871c chore(deps): update all non-major dependencies (#424)
  • 0c9e863 chore(deps): update devdependency @​types/jest to v28 (#426)
  • 694ba04 fix(deps): update devdependency @​sentry/webpack-plugin to ^1.19.0 (#434)
  • 2cf56ef feat: support for registering external integrations (#276)
  • 0f8242d chore(docs): specify that version 6 of tracing package needs to be used
  • 1da607c chore(deps): refresh lock file
  • 04706bb chore(deps): update all non-major dependencies (#421)
  • 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)

Merge request reports

Loading