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 @types/lodash from 4.14.150 to 4.14.153 #32

Merged
merged 2 commits into from
Oct 4, 2021

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade @types/lodash from 4.14.150 to 4.14.153.

merge advice

✨What is Merge Advice? We check thousands of dependency upgrade pull requests and CI tests every day to see which upgrades were successfully merged. After crunching this data, we give a recommendation on how safe we think the change is for you to merge without causing issues. Learn more, and share your feedback to help improve this feature. 🙏
ℹ️ 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 3 versions ahead of your current version.
  • The recommended version was released 2 days ago, on 2020-05-27.
Release notes
Package name: @types/lodash
  • 4.14.153 - 2020-05-27
  • 4.14.152 - 2020-05-19
  • 4.14.151 - 2020-05-15
  • 4.14.150 - 2020-04-17
from @types/lodash 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

@opyh opyh merged commit be6eb29 into master Oct 4, 2021
@opyh opyh deleted the snyk-upgrade-3f090a02b4dd17ae72c0895d1aaff8ba branch October 4, 2021 19:39
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