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

chore(deps): bump @sentry/browser from 7.120.0 to 8.42.0 in /frontend/benefit/handler #3624

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 3, 2024

Bumps @sentry/browser from 7.120.0 to 8.42.0.

Release notes

Sourced from @​sentry/browser's releases.

8.42.0

Important Changes

Deprecations

  • feat: Warn about source-map generation (#14533)

    In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application. Currently, the implementation varies a lot between different SDKs and can be difficult to understand. Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off. Additionally, if we end up enabling source maps, we will emit a log message that we did so.

    With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.

  • feat(nuxt): Deprecate tracingOptions in favor of vueIntegration (#14530)

    Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:

    • In Sentry.init()
    • Inside tracingOptions in Sentry.init()

    For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported vueIntegration() and its tracingOptions option to configure tracing options in the Nuxt SDK:

    // sentry.client.config.ts
    import * as Sentry from '@sentry/nuxt';
    Sentry.init({
    // ...
    integrations: [
    Sentry.vueIntegration({
    tracingOptions: {
    trackComponents: true,
    },
    }),
    ],
    });

Other Changes

  • feat(browser-utils): Update web-vitals to v4.2.4 (#14439)
  • feat(nuxt): Expose vueIntegration (#14526)
  • fix(feedback): Handle css correctly in screenshot mode (#14535)

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

8.42.0

Important Changes

Deprecations

  • feat: Warn about source-map generation (#14533)

    In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application. Currently, the implementation varies a lot between different SDKs and can be difficult to understand. Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off. Additionally, if we end up enabling source maps, we will emit a log message that we did so.

    With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.

  • feat(nuxt): Deprecate tracingOptions in favor of vueIntegration (#14530)

    Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:

    • In Sentry.init()
    • Inside tracingOptions in Sentry.init()

    For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported vueIntegration() and its tracingOptions option to configure tracing options in the Nuxt SDK:

    // sentry.client.config.ts
    import * as Sentry from '@sentry/nuxt';
    Sentry.init({
    // ...
    integrations: [
    Sentry.vueIntegration({
    tracingOptions: {
    trackComponents: true,
    },
    }),
    ],
    });

Other Changes

  • feat(browser-utils): Update web-vitals to v4.2.4 (#14439)
  • feat(nuxt): Expose vueIntegration (#14526)
  • fix(feedback): Handle css correctly in screenshot mode (#14535)

... (truncated)

Commits

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Bumps [@sentry/browser](https://github.com/getsentry/sentry-javascript) from 7.120.0 to 8.42.0.
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/8.42.0/CHANGELOG.md)
- [Commits](getsentry/sentry-javascript@7.120.0...8.42.0)

---
updated-dependencies:
- dependency-name: "@sentry/browser"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants