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 browserify from 16.5.0 to 16.5.1 #65

Merged
merged 1 commit into from Apr 30, 2020

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade browserify from 16.5.0 to 16.5.1.

ℹ️ 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 1 version ahead of your current version.
  • The recommended version was released 23 days ago, on 2020-03-30.

The recommended version fixes:

Severity Issue Exploit Maturity
Timing Attack
SNYK-JS-ELLIPTIC-511941
No Known Exploit
Release notes
Package name: browserify
  • 16.5.1 - 2020-03-30

    Remove deprecated mkdirp version in favour of mkdirp-classic.

    00c913f

    Pin dependencies for Node.js 0.8 support.

    #1939

  • 16.5.0 - 2019-08-09

    Support custom name for "browser" field resolution in package.json using the browserField option.

    #1918

from browserify GitHub release notes
Commit messages
Package name: browserify

Compare


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

@mandragorn mandragorn merged commit a51d48f into master Apr 30, 2020
@mandragorn mandragorn deleted the snyk-upgrade-3e347186807cd6c55adc48e952b3bed4 branch April 30, 2020 01:14
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