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 vis-network from 9.1.6 to 9.1.9 #5

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jihaui
Copy link
Owner

@jihaui jihaui commented Nov 24, 2023

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade vis-network from 9.1.6 to 9.1.9.

ℹ️ 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 3 versions ahead of your current version.
  • The recommended version was released 22 days ago, on 2023-11-03.
Release notes
Package name: vis-network
  • 9.1.9 - 2023-11-03

    9.1.9 (2023-11-03)

    Performance Improvements

    • remove add/remove event polyfills\n\nWe don't polyfill these browsers using core-js (i.e. it most likely doesn't work anyway) and barely anyone is using them nowadays. (#2039) (f1b7870)
  • 9.1.8 - 2023-10-15

    9.1.8 (2023-10-15)

    Bug Fixes

    • horizontal-strategy: add missing sort method (#2024) (d913165)
  • 9.1.7 - 2023-10-06

    9.1.7 (2023-10-06)

    Bug Fixes

  • 9.1.6 - 2023-03-23

    9.1.6 (2023-03-23)

    Bug Fixes

from vis-network GitHub release notes
Commit messages
Package name: vis-network

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

Copy link

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

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

Successfully merging this pull request may close these issues.

2 participants