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/nextjs from 7.91.0 to 7.93.0 #94

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

Conversation

Woodpile37
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade @sentry/nextjs from 7.91.0 to 7.93.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 2 versions ahead of your current version.
  • The recommended version was released 24 days ago, on 2024-01-10.
Release notes
Package name: @sentry/nextjs
  • 7.93.0 - 2024-01-10

    Important Changes

    Deprecations

    As we're moving closer to the next major version of the SDK, more public APIs were deprecated.

    To get a head start on migrating to the replacement APIs, please take a look at our
    migration guide.

    • feat(core): Deprecate getActiveTransaction() & scope.getTransaction() (#10098)
    • feat(core): Deprecate Hub.shouldSendDefaultPii (#10062)
    • feat(core): Deprecate new Transaction() (#10125)
    • feat(core): Deprecate scope.getSpan() & scope.setSpan() (#10114)
    • feat(core): Deprecate scope.setTransactionName() (#10113)
    • feat(core): Deprecate span.startChild() (#10091)
    • feat(core): Deprecate startTransaction() (#10073)
    • feat(core): Deprecate Transaction.getDynamicSamplingContext in favor of getDynamicSamplingContextFromSpan (#10094)
    • feat(core): Deprecate arguments for startSpan() (#10101)
    • feat(core): Deprecate hub capture APIs and add them to Scope (#10039)
    • feat(core): Deprecate session APIs on hub and add global replacements (#10054)
    • feat(core): Deprecate span name and description (#10056)
    • feat(core): Deprecate span tags, data, context & setters (#10053)
    • feat(core): Deprecate transaction metadata in favor of attributes (#10097)
    • feat(core): Deprecate span.sampled in favor of span.isRecording() (#10034)
    • ref(node-experimental): Deprecate lastEventId on scope (#10093)

    Cron Monitoring Support for node-schedule library

    This release adds auto instrumented check-ins for the node-schedule library.

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

    const scheduleWithCheckIn = Sentry.cron.instrumentNodeSchedule(schedule);

    const job = scheduleWithCheckIn.scheduleJob('my-cron-job', '* * * * *', () => {
    console.log('You will see this message every minute');
    });

    • feat(node): Instrumentation for node-schedule library (#10086)

    Other Changes

    • feat(core): Add span.spanContext() (#10037)
    • feat(core): Add spanToJSON() method to get span properties (#10074)
    • feat(core): Allow to pass scope to startSpan APIs (#10076)
    • feat(core): Allow to pass start/end timestamp for spans flexibly (#10060)
    • feat(node): Make getModuleFromFilename compatible with ESM (#10061)
    • feat(replay): Update rrweb to 2.7.3 (#10072)
    • feat(utils): Add parameterize function (#9145)
    • fix(astro): Use correct package name for CF (#10099)
    • fix(core): Do not run setup for integration on client multiple times (#10116)
    • fix(core): Ensure we copy passed in span data/tags/attributes (#10105)
    • fix(cron): Make name required for instrumentNodeCron option (#10070)
    • fix(nextjs): Don't capture not-found and redirect errors in generation functions (#10057)
    • fix(node): LocalVariables integration should have correct name (#10084)
    • fix(node): Anr events should have an event_id (#10068)
    • fix(node): Revert to only use sync debugger for LocalVariables (#10077)
    • fix(node): Update ANR min node version to v16.17.0 (#10107)

    Bundle size 📦

    Path Size
    @ sentry/browser (incl. Tracing, Replay, Feedback) - Webpack (gzipped) 76.98 KB
    @ sentry/browser (incl. Tracing, Replay) - Webpack (gzipped) 68.36 KB
    @ sentry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped) 61.99 KB
    @ sentry/browser (incl. Tracing) - Webpack (gzipped) 32.38 KB
    @ sentry/browser (incl. Feedback) - Webpack (gzipped) 30.98 KB
    @ sentry/browser - Webpack (gzipped) 22.31 KB
    @ sentry/browser (incl. Tracing, Replay, Feedback) - ES6 CDN Bundle (gzipped) 74.61 KB
    @ sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped) 66.26 KB
    @ sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped) 32.07 KB
    @ sentry/browser - ES6 CDN Bundle (gzipped) 23.9 KB
    @ sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed) 208.7 KB
    @ sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed) 96.75 KB
    @ sentry/browser - ES6 CDN Bundle (minified & uncompressed) 71.35 KB
    @ sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped) 35.04 KB
    @ sentry/react (incl. Tracing, Replay) - Webpack (gzipped) 68.72 KB
    @ sentry/react - Webpack (gzipped) 22.35 KB
    @ sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped) 85.37 KB
    @ sentry/nextjs Client - Webpack (gzipped) 49.5 KB
    @ sentry-internal/feedback - Webpack (gzipped) 17.01 KB
  • 7.92.0 - 2024-01-04
    Read more
  • 7.91.0 - 2023-12-22
    Read more
from @sentry/nextjs 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

Copy link

changeset-bot bot commented Feb 4, 2024

⚠️ No Changeset found

Latest commit: 58acda3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@sentry/nextjs@7.93.0 environment, filesystem, network Transitive: eval, shell, unsafe +159 1.19 GB sentry-bot

🚮 Removed packages: npm/@sentry/nextjs@7.91.0

View full report↗︎

Copy link

codeautopilot bot commented Feb 4, 2024

PR summary

The Pull Request (PR) is an automated update by Snyk to upgrade the @sentry/nextjs package from version 7.91.0 to 7.93.0. The upgrade includes several important changes, deprecations, and new features.

Implications and Purpose

  • Deprecations: Several public APIs are deprecated as Sentry prepares for the next major version of the SDK. Users are encouraged to migrate to replacement APIs using the provided migration guide.
  • Cron Monitoring: Adds support for auto-instrumented check-ins for the node-schedule library, which can be useful for monitoring scheduled tasks.
  • Other Changes: Includes various new features, improvements, and bug fixes, such as new methods for working with spans, compatibility updates, and bundle size information.

Impact

  • Users of the @sentry/nextjs package will benefit from the new features and improvements.
  • Projects using deprecated APIs will need to plan for migration to avoid future issues when the next major version is released.
  • The bundle size information provided can help users understand the impact of Sentry on their application's load time.

Suggestion

  • Review the deprecations and start planning for migration to the new APIs.
  • Test the new version in a development environment to ensure compatibility and to take advantage of the new features.
  • Monitor the application after updating to check for any unexpected behavior or issues.

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 63.94%

Have feedback or need help?
Discord
Documentation
support@codeautopilot.com

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