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

fix(deps): update dependency @sentry/node to v8 #2

Merged
merged 1 commit into from
May 26, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 26, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change OpenSSF
@sentry/node (source) dependencies major 7.116.0 -> 8.4.0 OpenSSF Scorecard

Release Notes

getsentry/sentry-javascript (@​sentry/node)

v8.4.0

Compare Source

Important Changes
  • feat(nextjs): Trace pageloads in App Router (#​12157)

If you are using Next.js version 14.3.0-canary.64 or above, the Sentry Next.js SDK will now trace clientside pageloads
with React Server Components. This means, that client-side errors like
Error: An error occurred in the Server Components render., which previously didn't give you much information on how
that error was caused, can now be traced back to a specific error in a server component.

  • feat(angular): Add Support for Angular 18 (#​12183)

This release guarantees support for Angular 18 with @sentry/angular.

Other Changes

v8.3.0

Compare Source

Important Changes
  • Better Node Framework Span Data

This release improves data quality of spans emitted by Express, Fastify, Connect, Koa, Nest.js and Hapi.

When using Sentry in ESM mode, you can now use Sentry without manually calling init like this:

 SENTRY_DSN=https://[email protected]/0 node --import=@​sentry/node/init app.mjs

When using CommonJS, you can do:

 SENTRY_DSN=https://[email protected]/0 node --require=@​sentry/node/init app.js
Other Changes
  • chore: Align and update MIT license dates (#​12143)
  • chore: Resolve or postpone a random assortment of TODOs (#​11977)
  • doc(migration): Add entry for runWithAsyncContext (#​12153)
  • docs: Add migration docs to point out that default import does not work (#​12100)
  • docs(sveltekit): process.env.SENTRY_AUTH_TOKEN (#​12118)
  • feat(browser): Ensure browserProfilingIntegration is published to CDN (#​12158)
  • feat(google-cloud): Expose ESM build (#​12149)
  • feat(nextjs): Ignore Prisma critical dependency warnings (#​12144)
  • feat(node): Add app.free_memory info to events (#​12150)
  • feat(node): Do not create GraphQL resolver spans by default (#​12097)
  • feat(node): Use node: prefix for node built-ins (#​11895)
  • feat(replay): Use unwrapped setTimeout to avoid e.g. angular change detection (#​11924)
  • fix(core): Add dsn to span envelope header (#​12096)
  • fix(feedback): Improve feedback border color in dark-mode, and prevent auto-dark mode when a theme is picked (#​12126)
  • fix(feedback): Set optionOverrides to be optional in TS definition (#​12125)
  • fix(nextjs): Don't put undefined values in props (#​12131)
  • fix(nextjs): Fix legacy configuration method detection for emitting warning (#​12136)
  • fix(node): Ensure fetch/http breadcrumbs are created correctly (#​12137)
  • fix(node): Update @prisma/instrumentation from 5.13.0 to 5.14.0 (#​12081)
  • ref(node): Add log for running in ESM/CommonJS mode (#​12134)
  • ref(node): Handle failing hook registration gracefully (#​12135)
  • ref(node): Only show instrumentation warning when tracing is enabled (#​12141)

Work in this release contributed by @​pboling. Thank you for your contribution!

v8.2.1

Compare Source

  • fix(aws-serverless): Fix build of lambda layer (#​12083)
  • fix(nestjs): Broaden nest.js type (#​12076)

v8.2.0

Compare Source

  • feat(redis-cache): Create cache-span with prefixed keys (get/set commands) (#​12070)
  • feat(core): Add beforeSendSpan hook (#​11886)
  • feat(browser): Improve idle span handling (#​12065)
  • fix(node): Set transactionName for unsampled spans in httpIntegration (#​12071)
  • fix(core): Export Scope interface as Scope (#​12067)
  • fix(core): Avoid looking up client for hasTracingEnabled() if possible (#​12066)
  • fix(browser): Use consistent timestamps (#​12063)
  • fix(node): Fix check for performance integrations (#​12043)
  • ref(sveltekit): Warn to delete source maps if Sentry plugin enabled source maps generation (#​12072)

v8.1.0

Compare Source

This release mainly fixes a couple of bugs from the initial 8.0.0 release. In addition to the changes below, we
updated some initially missed points in our migration guides and documentation.

  • feat(aws-serverless): Fix tree-shaking for aws-serverless package (#​12017)
  • feat(node): Bump opentelemetry instrumentation to latest version (#​12028)
  • feat(scope): Bring back lastEventId on isolation scope (#​11951) (#​12022)
  • fix(aws-serverless): Export awslambda-auto
  • fix(node): Do not warn for missing instrumentation if SDK is disabled (#​12041)
  • fix(react): Set dependency-injected functions as early as possible (#​12019)
  • fix(react): Warn and fall back gracefully if dependency injected functions are not available (#​12026)
  • ref(core): Streamline parseSampleRate utility function (#​12024)
  • ref(feedback): Make eventId optional and use lastEventId in report dialog (#​12029)

v8.0.0

Compare Source

Important Changes
  • feat(bun): Add Bun Global Unhandled Handlers (#​11960)

The Bun SDK will now capture global unhandled errors.

Other Changes
  • feat(node): Log process and thread info on initialisation (#​11972)
  • fix(aws-serverless): Include ESM artifacts in package (#​11973)
  • fix(browser): Only start http.client spans if there is an active parent span (#​11974)
  • fix(feedback): Improve CSS theme variable names and layout (#​11964)
  • fix(node): Ensure execArgv are not sent to worker threads (#​11963)
  • ref(feedback): Simplify feedback function params (#​11957)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link

changeset-bot bot commented May 26, 2024

⚠️ No Changeset found

Latest commit: 6abd6ef

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@gipo355 gipo355 force-pushed the renovate/major-sentry-javascript-monorepo branch from 1557f89 to 6abd6ef Compare May 26, 2024 21:04
@gipo355 gipo355 merged commit 1b116ed into main May 26, 2024
7 checks passed
@gipo355 gipo355 deleted the renovate/major-sentry-javascript-monorepo branch May 26, 2024 21:04
Copy link

nx-cloud bot commented May 26, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 6abd6ef. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 1 target

Sent with 💌 from NxCloud.

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.

1 participant