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 npm from 6.11.3 to 6.12.0 #58

Closed

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade npm from 6.11.3 to 6.12.0.

  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released 9 days ago, on 2019-10-08.
Release notes

from npm GitHub Release Notes


🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@vercel
Copy link

vercel bot commented Oct 18, 2019

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/fast-start/expressjs-opensource/n8238we94
🌍 Preview: https://expressjs-open-git-snyk-upgrade-f41eec83be5c6d73daa20fb4-0ca354.fast-start1.now.sh

@codecov-io
Copy link

codecov-io commented Oct 18, 2019

Codecov Report

Merging #58 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master     #58   +/-   ##
======================================
  Coverage    45.2%   45.2%           
======================================
  Files          27      27           
  Lines         292     292           
  Branches       31      31           
======================================
  Hits          132     132           
  Misses        145     145           
  Partials       15      15

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 66b098b...388f3ab. Read the comment docs.

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.

3 participants