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/node from 5.9.0 to 5.15.4 #376

Closed

Conversation

snyk-bot
Copy link
Contributor

@snyk-bot snyk-bot commented May 5, 2020

Snyk has created this PR to upgrade @sentry/node from 5.9.0 to 5.15.4.

ℹ️ 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 29 versions ahead of your current version.
  • The recommended version was released a month ago, on 2020-03-27.
Release notes
Package name: @sentry/node
  • 5.15.4 - 2020-03-27
    • [node] fix: Path domain onto global extension method to not use require (#2527)
  • 5.15.3 - 2020-03-27
    • [hub] fix: Restore dynamicRequire, but for perf_hooks only (#2524)
  • 5.15.2 - 2020-03-26
    • [hub] fix: Remove dynamicRequire, Fix require call (#2521)
  • 5.15.1 - 2020-03-26
    • [browser] fix: Prevent crash for react native instrumenting fetch (#2510)
    • [node] fix: Remove the no longer required dynamicRequire hack to fix scope memory leak (#2515)
    • [node] fix: Guard against invalid req.user input (#2512)
    • [node] ref: Move node version to runtime context (#2507)
    • [utils] fix: Make sure that SyncPromise handler is called only once (#2511)
  • 5.15.0 - 2020-03-20
    • [apm] fix: Sampling of traces work now only depending on the client option tracesSampleRate (#2500)
    • [apm] fix: Remove internal forceNoChild parameter from hub.startSpan (#2500)
    • [apm] fix: Made constructor of Span internal, only use hub.startSpan (#2500)
    • [apm] ref: Remove status from tags in transaction (#2497)
    • [browser] fix: Respect breadcrumbs sentry:false option (#2499)
    • [node] ref: Skip body parsing for GET/HEAD requests (#2504)
  • 5.14.2 - 2020-03-13
    • [apm] fix: Use Performance API for timings when available, including Web Workers (#2492)
    • [apm] fix: Remove Performance references (#2495)
    • [apm] fix: Set op in node http.server transaction (#2496)
  • 5.14.1 - 2020-03-12
    • [apm] fix: Check for performance.timing in webworkers (#2491)
    • [apm] ref: Remove performance clear entry calls (#2490)
  • 5.14.0 - 2020-03-11
    • [apm] feat: Add a simple heartbeat check, if activities don't change in 3 beats, finish the transaction (#2478)
    • [apm] feat: Make use of the performance browser API to provide better instrumentation (#2474)
    • [browser] ref: Move global error handler + unhandled promise rejection to instrument (#2475)
    • [apm] ref: Always use monotonic clock for time calculations (#2485)
    • [apm] fix: Add trace context to all events (#2486)
  • 5.13.2 - 2020-03-05
    • [apm] feat: Add discardBackgroundSpans to discard background spans by default
  • 5.13.1 - 2020-02-28
  • 5.13.0 - 2020-02-28
  • 5.12.5 - 2020-02-26
  • 5.12.4 - 2020-02-19
  • 5.12.3 - 2020-02-04
  • 5.12.2 - 2020-02-04
  • 5.12.1 - 2020-02-04
  • 5.12.0 - 2020-02-03
  • 5.11.2 - 2020-01-29
  • 5.11.1 - 2020-01-15
  • 5.11.0 - 2020-01-08
  • 5.10.2 - 2019-12-09
  • 5.10.1 - 2019-12-05
  • 5.10.0 - 2019-12-04
  • 5.10.0-rc.0 - 2019-11-27
  • 5.10.0-beta.4 - 2019-11-22
  • 5.10.0-beta.3 - 2019-11-20
  • 5.10.0-beta.2 - 2019-11-19
  • 5.10.0-beta.1 - 2019-11-19
  • 5.10.0-beta.0 - 2019-11-15
  • 5.9.0 - 2019-11-13
from @sentry/node 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

@adityapahuja adityapahuja deleted the snyk-upgrade-10e1ee33d195dbdd19a3cccbbc92a6a5 branch February 5, 2021 10:31
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.

None yet

2 participants