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 from 5.7.0 to 5.16.0 #6

Merged
merged 1 commit into from
Apr 10, 2022

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Apr 7, 2022

Snyk has created this PR to upgrade d3 from 5.7.0 to 5.16.0.

ℹ️ 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 23 versions ahead of your current version.
  • The recommended version was released 2 years ago, on 2020-04-20.
Release notes
Package name: d3
  • 5.16.0 - 2020-04-20
  • 5.15.1 - 2020-04-01
  • 5.15.0 - 2019-12-29
  • 5.14.2 - 2019-11-20
  • 5.14.1 - 2019-11-17
  • 5.14.0 - 2019-11-17
  • 5.13.1 - 2019-11-16
  • 5.13.0 - 2019-11-16
  • 5.12.0 - 2019-09-07
  • 5.11.0 - 2019-08-21
  • 5.10.1 - 2019-08-21
  • 5.10.0 - 2019-08-19
  • 5.9.7 - 2019-06-28
  • 5.9.6 - 2019-06-28
  • 5.9.5 - 2019-06-27
  • 5.9.4 - 2019-06-26
  • 5.9.3 - 2019-06-26
  • 5.9.2 - 2019-03-14
  • 5.9.1 - 2019-02-10
  • 5.9.0 - 2019-02-07
  • 5.8.2 - 2019-02-05
  • 5.8.1 - 2019-02-04
  • 5.8.0 - 2019-01-28
  • 5.7.0 - 2018-08-24
from d3 GitHub release notes
Commit messages
Package name: d3

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

@jj-crypto jj-crypto merged commit 4f586f8 into master Apr 10, 2022
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