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

fix(deps): update dependency chalk to v4 #617

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 2, 2020

This PR contains the following updates:

Package Type Update Change
chalk dependencies major ^3.0.0 -> ^4.0.0

Release Notes

chalk/chalk

v4.0.0

Compare Source

Breaking
  • Require Node.js 10 61999a4
  • Change the Level TypeScript type to be a union instead of enum f0f4638
-if (chalk.level > Level.None) {}
+if (chalk.level > 0) {}
Improvements
  • Use Object.setPrototypeOf as __proto__ could potentially be disabled (#​387) 63469d3

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

@coveralls
Copy link

coveralls commented Apr 2, 2020

Coverage Status

Coverage remained the same at 92.714% when pulling 7ac9bc5 on renovate/chalk-4.x into 9bca41d on master.

@renovate renovate bot force-pushed the renovate/chalk-4.x branch 3 times, most recently from 7ac9bc5 to e956392 Compare May 8, 2020 18:30
Signed-off-by: Renovate Bot <bot@renovateapp.com>
@bcoe bcoe closed this May 8, 2020
@bcoe bcoe deleted the renovate/chalk-4.x branch May 8, 2020 18:55
@renovate
Copy link
Contributor Author

renovate bot commented May 8, 2020

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 4.x releases. However, if you upgrade to 4.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

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

Successfully merging this pull request may close these issues.

None yet

3 participants