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.15.0 to 5.15.2 #116

Merged
merged 1 commit into from
Mar 31, 2020

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade @sentry/node from 5.15.0 to 5.15.2.

ℹ️ 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 2 days ago, on 2020-03-26.
Release notes
Package name: @sentry/node
  • 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)
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

@codeclimate
Copy link

codeclimate bot commented Mar 29, 2020

Code Climate has analyzed commit ea0fbb1 and detected 0 issues on this pull request.

View more on Code Climate.

@TobiTenno TobiTenno merged commit 1a6f71a into master Mar 31, 2020
@TobiTenno TobiTenno deleted the snyk-upgrade-5753f5bc696ea0c9898d585a90178fa2 branch March 31, 2020 23:12
TobiTenno pushed a commit that referenced this pull request May 16, 2020
chore: upgrade warframe-items from 1.842.0 to 1.855.0 (#96)

chore(package): upgrade helmet from 3.21.1 to 3.21.3 (#98)

chore(package): upgrade warframe-worldstate-data from 1.3.10 to 1.3.12 (#99)

chore(package): upgrade apicache from 1.5.2 to 1.5.3 (#100)

chore(package): upgrade @sentry/node from 5.14.0 to 5.14.1 (#101)

chore(package): upgrade warframe-worldstate-data from 1.3.12 to 1.4.0 (#102)

chore(package): upgrade warframe-items from 1.855.0 to 1.856.0 (#104)

chore(package): upgrade warframe-worldstate-parser from 2.10.5 to 2.10.6 (#103)

chore(package): upgrade @sentry/node from 5.14.1 to 5.14.2 (#106)

chore(package): upgrade @sentry/node from 5.14.2 to 5.15.0 (#110)

chore(package): upgrade warframe-items from 1.856.0 to 1.857.0 (#109)

chore(package): upgrade json-fetch-cache from 1.2.3 to 1.2.4 (#108)

chore(package): upgrade warframe-items from 1.857.0 to 1.859.0 (#111)

chore(package): upgrade warframe-nexus-query from 1.6.7 to 1.6.9 (#107)

chore(package): upgrade helmet from 3.21.3 to 3.22.0 (#113)

chore(package): upgrade warframe-items from 1.859.0 to 1.865.0 (#112)

fix: check for inner object before assignment

chore(package): upgrade warframe-items from 1.865.0 to 1.867.0 (#114)

chore(package): upgrade warframe-worldstate-data from 1.4.0 to 1.4.1 (#115)

chore(package): upgrade warframe-worldstate-data from 1.4.1 to 1.4.3 (#119)

chore(package): upgrade @sentry/node from 5.15.0 to 5.15.2 (#116)

chore(package): upgrade warframe-items from 1.867.0 to 1.869.0 (#117)

chore(package): upgrade warframe-worldstate-parser from 2.10.6 to 2.11.0 (#118)

chore(package): upgrade warframe-worldstate-parser from 2.11.0 to 2.11.1 (#122)

chore(package): upgrade @sentry/node from 5.15.2 to 5.15.4 (#120)

chore(package): upgrade warframe-worldstate-parser from 2.11.1 to 2.11.2 (#124)

chore(package): upgrade warframe-items from 1.869.0 to 1.877.0 (#125)

chore(package): upgrade warframe-items from 1.877.0 to 1.878.0 (#126)

chore(package): upgrade warframe-items from 1.878.0 to 1.879.0 (#130)

chore(package): upgrade warframe-worldstate-data from 1.4.3 to 1.4.4 (#129)

chore(package): upgrade warframe-worldstate-parser from 2.11.2 to 2.11.3 (#128)

chore(package): upgrade warframe-nexus-query from 1.6.9 to 1.6.11 (#127)

chore(package): upgrade warframe-items from 1.879.0 to 1.880.0 (#131)

chore(package): upgrade warframe-nexus-query from 1.6.11 to 1.6.12 (#134)

chore(package): upgrade warframe-worldstate-parser from 2.11.3 to 2.12.0 (#133)

chore(package): upgrade warframe-worldstate-data from 1.4.4 to 1.4.7 (#132)

chore(package): upgrade warframe-items from 1.880.0 to 1.883.0 (#135)

chore(package): upgrade warframe-worldstate-data from 1.4.7 to 1.4.8 (#136)

chore(package): upgrade warframe-items from 1.883.0 to 1.884.0 (#137)

chore(package): upgrade warframe-items from 1.884.0 to 1.885.0 (#138)

chore(package): upgrade warframe-items from 1.885.0 to 1.891.0 (#139)

chore(package): upgrade @sentry/node from 5.15.4 to 5.15.5 (#140)

chore(package): upgrade warframe-worldstate-data from 1.4.8 to 1.4.9

chore(package): upgrade warframe-worldstate-data from 1.4.9 to 1.4.10 (#142)

chore(security): [Snyk] Fix for 1 vulnerabilities (#143)

chore(package): upgrade warframe-worldstate-parser from 2.12.0 to 2.13.0 (#144)

chore(package): upgrade warframe-worldstate-parser from 2.13.0 to 2.13.1 (#145)

chore(package): upgrade warframe-worldstate-data from 1.4.10 to 1.4.24 (#146)
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