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 chalk from 4.1.1 to 4.1.2 #92

Merged

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade chalk from 4.1.1 to 4.1.2.

merge advice
ℹ️ 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 a day ago, on 2021-07-30.
Release notes
Package name: chalk from chalk GitHub release notes
Commit messages
Package name: chalk

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

@tobiasbueschel tobiasbueschel merged commit c35683f into master Aug 6, 2021
@tobiasbueschel tobiasbueschel deleted the snyk-upgrade-9a16d0e96ad2410392e4f1d2aa46e506 branch August 6, 2021 01:59
github-actions bot pushed a commit that referenced this pull request Aug 6, 2021
## [1.3.13](v1.3.12...v1.3.13) (2021-08-06)

### Bug Fixes

* upgrade chalk from 4.1.1 to 4.1.2 ([#92](#92)) ([c35683f](c35683f))
* upgrade git-url-parse from 11.4.4 to 11.5.0 ([#91](#91)) ([919e1e7](919e1e7))
@github-actions
Copy link

github-actions bot commented Aug 6, 2021

🎉 This PR is included in version 1.3.13 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants