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 d3-scale from 2.1.2 to 3.2.1 #1821

Closed

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade d3-scale from 2.1.2 to 3.2.1.

ℹ️ 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.

Warning: This is a major version upgrade, and may be a breaking change.

  • The recommended version is 8 versions ahead of your current version.
  • The recommended version was released 4 months ago, on 2019-11-23.
Release notes
Package name: d3-scale from d3-scale GitHub release notes
Commit messages
Package name: d3-scale

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

@shaundon shaundon closed this Mar 13, 2020
@shaundon shaundon deleted the snyk-upgrade-c5f20560a19e27813b429831179670c6 branch March 13, 2020 08:36
@backpackbot
Copy link

Warnings
⚠️

One or more packages have changed, but UNRELEASED.yaml wasn't updated.

Hi snyk-bot!

Thanks for the PR 🎉! Contributions like yours help to improve the design system
for everybody and we appreciate you taking the effort to create this PR.

Thanks

If you're curious about how we review, please read through the
code review guidelines.

Generated by 🚫 dangerJS against 1af3eaa

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