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: , , , next #37

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

Conversation

onsails
Copy link
Member

@onsails onsails commented Sep 18, 2024

snyk-top-banner

Snyk has created this PR to upgrade multiple dependencies.

👯 The following dependencies are linked and will therefore be updated together.

ℹ️ 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.

Name Versions Released on

@floating-ui/react
from 0.26.22 to 0.26.23 | 1 version ahead of your current version | 24 days ago
on 2024-08-25
@sentry/nextjs
from 8.26.0 to 8.27.0 | 1 version ahead of your current version | 22 days ago
on 2024-08-27
@t3-oss/env-nextjs
from 0.11.0 to 0.11.1 | 1 version ahead of your current version | 24 days ago
on 2024-08-25
next
from 14.2.6 to 14.2.7 | 1 version ahead of your current version | 22 days ago
on 2024-08-27

Release notes
Package name: @floating-ui/react
  • 0.26.23 - 2024-08-25

    Patch Changes

    • feat: add onOpenChange reason string for FloatingFocusManager's closeOnFocusOut handling
    • fix(inner): correctly handle borders
    • fix(FloatingArrow): ignore staticOffset prop if floating element is shifted. Fixes an issue where the arrow could potentially point to nothing if it was shifted enough from its reference element.
    • fix(useListNavigation, Composite): prevent onNavigate from potentially passing in an undefined value instead of null
    • fix(useHover): blockPointerEvents no longer adds pointer-events: none to unintended <body> elements.
    • fix: manage focus on element with floating props spread on it
    • fix(FloatingFocusManager): support keepMounted behavior with disabled prop
  • 0.26.22 - 2024-08-07

    Patch Changes

from @floating-ui/react GitHub release notes
Package name: @sentry/nextjs
  • 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

    Important Changes

    • feat(node): Add fsInstrumentation (#13291)

      This release adds fsIntegration, an integration that instruments the fs API to the Sentry Node SDK. The
      integration creates spans with naming patterns of fs.readFile, fs.unlink, and so on.

      This integration is not enabled by default and needs to be registered in your Sentry.init call. You can configure
      via options whether to include path arguments or error messages as span attributes when an fs call fails:

      Sentry.init({
        integrations: [
          Sentry.fsIntegration({
            recordFilePaths: true,
            recordErrorMessagesAsSpanAttributes: true,
          }),
        ],
      });

      WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of
      file I/O, like for example when running a framework dev server, including this integration can massively slow down
      your application.

    Other Changes

    • feat(browser): Add spotlightBrowser integration (#13263)

    • feat(browser): Allow sentry in safari extension background page (#13209)

    • feat(browser): Send CLS as standalone span (experimental) (#13056)

    • feat(core): Add OpenTelemetry-specific getTraceData implementation (#13281)

    • feat(nextjs): Always add browserTracingIntegration (#13324)

    • feat(nextjs): Always transmit trace data to the client (#13337)

    • feat(nextjs): export SentryBuildOptions (#13296)

    • feat(nextjs): Update experimental_captureRequestError to reflect RequestInfo.path change in Next.js canary
      (#13344)

    • feat(nuxt): Always add tracing meta tags (#13273)

    • feat(nuxt): Set transaction name for server error (#13292)

    • feat(replay): Add a replay-specific logger (#13256)

    • feat(sveltekit): Add bundle size optimizations to plugin options (#13318)

    • feat(sveltekit): Always add browserTracingIntegration (#13322)

    • feat(tracing): Make long animation frames opt-out (#13255)

    • fix(astro): Correctly extract request data (#13315)

    • fix(astro): Only track access request headers in dynamic page requests (#13306)

    • fix(nuxt): Add import line for disabled autoImport (#13342)

    • fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)

    • fix(opentelemetry): Do not overwrite http span name if kind is internal (#13282)

    • fix(remix): Ensure origin is correctly set for remix server spans (#13305)

    Work in this release was contributed by @ MonstraG, @ undead-voron and @ Zen-cronic. Thank you for your contributions!

from @sentry/nextjs GitHub release notes
Package name: @t3-oss/env-nextjs from @t3-oss/env-nextjs GitHub release notes
Package name: next
  • 14.2.7 - 2024-08-27

    Note

    This release is backporting bug fixes. It does not include all pending features/changes on canary.

    Core Changes

    • Revert "chore: externalize undici for bundling" (#65727)
    • Refactor internal routing headers to use request meta (#66987)
    • fix(next): add cross origin in react dom preload (#67423)
    • build: upgrade edge-runtime (#67565)
    • GTM dataLayer parameter should take an object, not an array of strings (#66339)
    • fix: properly patch lockfile against swc bindings (#66515)
    • Add deployment id header for rsc payload if present (#67255)
    • Update font data (#68639)
    • fix i18n data pathname resolving (#68947)
    • pages router: ensure x-middleware-cache is respected (#67734)
    • Fix bad modRequest in flight entry manifest #68888
    • Reject next image urls in image optimizer #68628
    • Fix hmr assetPrefix escaping and reuse logic from other files #67983

    Credits

    Huge thanks to @ kjugi, @ huozhi, @ ztanner, @ SukkaW, @ marlier, @ Kikobeats, @ syi0808, @ ijjk, and @ samcx for helping!

  • 14.2.6 - 2024-08-21
from next GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

Snyk has created this PR to upgrade:
  - @floating-ui/react from 0.26.22 to 0.26.23.
    See this package in npm: https://www.npmjs.com/package/@floating-ui/react
  - @sentry/nextjs from 8.26.0 to 8.27.0.
    See this package in npm: https://www.npmjs.com/package/@sentry/nextjs
  - @t3-oss/env-nextjs from 0.11.0 to 0.11.1.
    See this package in npm: https://www.npmjs.com/package/@t3-oss/env-nextjs
  - next from 14.2.6 to 14.2.7.
    See this package in npm: https://www.npmjs.com/package/next

See this project in Snyk:
https://app.snyk.io/org/haqq-ud4/project/b9365018-f88d-493c-9d4d-d75074b6b540?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Sep 18, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
islamic-website ❌ Failed (Inspect) Sep 18, 2024 8:38am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants