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

[Snyk] Upgrade @sentry/angular from 8.26.0 to 8.30.0 #1612

Closed

Conversation

cvs-ops
Copy link
Contributor

@cvs-ops cvs-ops commented Oct 9, 2024

Snyk has created this PR to upgrade @sentry/angular from 8.26.0 to 8.30.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 4 versions ahead of your current version.
  • The recommended version was released a month ago, on 2024-09-10.
Release notes
Package name: @sentry/angular
  • 8.30.0 - 2024-09-10

    Important Changes

    • feat(node): Add kafkajs integration (#13528)

    This release adds a new integration that instruments kafkajs library with spans and traces. This integration is
    automatically enabled by default, but can be included with the Sentry.kafkaIntegration() import.

    Sentry.init({
      integrations: [Sentry.kafkaIntegration()],
    });

    Other Changes

    • feat(core): Allow adding measurements without global client (#13612)
    • feat(deps): Bump @ opentelemetry/instrumentation-undici from 0.5.0 to 0.6.0 (#13622)
    • feat(deps): Bump @ sentry/cli from 2.33.0 to 2.35.0 (#13624)
    • feat(node): Use @ opentelemetry/instrumentation-undici for fetch tracing (#13485)
    • feat(nuxt): Add server config to root folder (#13583)
    • feat(otel): Upgrade @ opentelemetry/semantic-conventions to 1.26.0 (#13631)
    • fix(browser): check supportedEntryTypes before caling the function (#13541)
    • fix(browser): Ensure Standalone CLS span timestamps are correct (#13649)
    • fix(nextjs): Widen removal of 404 transactions (#13628)
    • fix(node): Remove ambiguity and race conditions when matching local variables to exceptions (#13501)
    • fix(node): Update OpenTelemetry instrumentation package for solidstart and opentelemetry (#13640)
    • fix(node): Update OpenTelemetry instrumentation package for solidstart and opentelemetry (#13642)
    • fix(vue): Ensure Vue trackComponents list matches components with or without <> (#13543)
    • ref(profiling): Conditionally shim cjs globals (#13267)

    Work in this release was contributed by @ Zen-cronic and @ odanado. Thank you for your contributions!

  • 8.29.0 - 2024-09-09

    Important Changes

    • Beta releases of official Solid and SolidStart Sentry SDKs

    This release marks the beta releases of the @ sentry/solid and @ sentry/solidstart Sentry SDKs. For details on how to
    use them, check out the
    Sentry Solid SDK README and the
    Sentry SolidStart SDK README
    respectively. Please reach out on GitHub if you have
    any feedback or concerns.

    • feat(node): Option to only wrap instrumented modules (#13139)

    Adds the SDK option to only wrap ES modules with import-in-the-middle that specifically need to be instrumented.

    import * as Sentry from '@ sentry/node';

    Sentry.init({
    dsn: 'PUBLIC_DSN',
    registerEsmLoaderHooks: { onlyIncludeInstrumentedModules: true },
    });

    • feat(node): Update OpenTelemetry packages to instrumentation v0.53.0 (#13587)

    All internal OpenTelemetry instrumentation was updated to their latest version. This adds support for Mongoose v7 and v8
    and fixes various bugs related to ESM mode.

    Other Changes

    • feat(nextjs): Emit warning when using turbopack (#13566)
    • feat(nextjs): Future-proof Next.js config options overriding (#13586)
    • feat(node): Add generic-pool integration (#13465)
    • feat(nuxt): Upload sourcemaps generated by Nitro (#13382)
    • feat(solidstart): Add browserTracingIntegration by default (#13561)
    • feat(solidstart): Add sentrySolidStartVite plugin to simplify source maps upload (#13493)
    • feat(vue): Only start UI spans if parent is available (#13568)
    • fix(cloudflare): Guard context.waitUntil call in request handler (#13549)
    • fix(gatsby): Fix assets path for sourcemaps upload (#13592)
    • fix(nextjs): Use posix paths for sourcemap uploads (#13603)
    • fix(node-fetch): Use stringified origin url (#13581)
    • fix(node): Replace dashes in generic-pool span origins with underscores (#13579)
    • fix(replay): Fix types in WebVitalData (#13573)
    • fix(replay): Improve replay web vital types (#13602)
    • fix(utils): Keep logger on carrier (#13570)

    Work in this release was contributed by @ Zen-cronic. Thank you for your contribution!

  • 8.28.0 - 2024-09-03
    Read more
  • 8.27.0 - 2024-08-27

    Important Changes

    • fix(nestjs): Exception filters in main app module are not being executed (#13278)

      With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule to your
      application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to
      your main module providers or decorate the catch() method in your existing global exception filters with the newly
      released @ WithSentry() decorator. See the docs for
      more details.

    Other Changes

    • feat: Add options for passing nonces to feedback integration (#13347)
    • feat: Add support for SENTRY_SPOTLIGHT env var in Node (#13325)
    • feat(deps): bump @ prisma/instrumentation from 5.17.0 to 5.18.0 (#13327)
    • feat(feedback): Improve error message for 403 errors (#13441)
    • fix(deno): Don't rely on Deno.permissions.querySync (#13378)
    • fix(replay): Ensure we publish replay CDN bundles (#13437)

    Work in this release was contributed by @ charpeni. Thank you for your contribution!

  • 8.26.0 - 2024-08-14
from @sentry/angular GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@github-actions github-actions bot added the merge conflict PR needs rebasing label Oct 29, 2024
@pbardy2000
Copy link
Contributor

Closing as this is handled by #1627

@pbardy2000 pbardy2000 closed this Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge conflict PR needs rebasing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants