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 detect-browser from 5.1.1 to 5.2.0 #2373

Merged
merged 1 commit into from
Oct 30, 2020

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade detect-browser from 5.1.1 to 5.2.0.

merge advice

✨ Snyk has automatically assigned this pull request, set who gets assigned.
ℹ️ 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 21 days ago, on 2020-10-08.
Release notes
Package name: detect-browser from detect-browser GitHub release notes
Commit messages
Package name: detect-browser

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

👩‍💻 Set who automatically gets assigned

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@snyk-bot snyk-bot requested a review from bsekachev as a code owner October 29, 2020 22:02
@coveralls
Copy link

Coverage Status

Coverage remained the same at 60.663% when pulling bac7c7c on snyk-upgrade-0708e262410ecea6bab473f127ec5831 into 947d356 on develop.

@bsekachev bsekachev merged commit 373d94c into develop Oct 30, 2020
@bsekachev bsekachev deleted the snyk-upgrade-0708e262410ecea6bab473f127ec5831 branch November 3, 2020 10: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.

3 participants