Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

[Snyk] Upgrade @types/yeoman-environment from 2.3.2 to 2.3.3 #24

Closed

Conversation

snyk-bot
Copy link
Contributor

@snyk-bot snyk-bot commented May 7, 2020

Snyk has created this PR to upgrade @types/yeoman-environment from 2.3.2 to 2.3.3.

merge advice

鉁╓hat 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. 馃檹
As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

鈩癸笍 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 2 months ago, on 2020-02-27.
Release notes
Package name: @types/yeoman-environment
  • 2.3.3 - 2020-02-27
  • 2.3.2 - 2019-07-31
from @types/yeoman-environment 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

@wjhsf wjhsf mentioned this pull request May 7, 2020
@wjhsf
Copy link
Contributor

wjhsf commented May 7, 2020

Closing in favor of #25.

@wjhsf wjhsf closed this May 7, 2020
@wjhsf wjhsf deleted the snyk-upgrade-e00f5ded6b9ef96c2c2f797f90012222 branch May 7, 2020 15:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants