[Snyk] Upgrade @sentry/node from 5.14.1 to 5.14.2 #106
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade @sentry/node from 5.14.1 to 5.14.2. See this package in NPM: https://www.npmjs.com/package/@sentry/node See this project in Snyk: https://app.snyk.io/org/tobitenno/project/ed8fc95c-1093-46d0-b5a9-710045413f1e?utm_source=github&utm_medium=upgrade-pr
|
Code Climate has analyzed commit a0a5189 and detected 0 issues on this pull request. View more on Code Climate. |
TobiTenno
approved these changes
Mar 19, 2020
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade @sentry/node from 5.14.1 to 5.14.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.Release notes
Package name: @sentry/node
-
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
-
5.14.1 - 2020-03-12
- [apm] fix: Check for performance.timing in webworkers (#2491)
- [apm] ref: Remove performance clear entry calls (#2490)
from @sentry/node GitHub release notesopin node http.server transaction (#2496)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