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 vald-client-node from 1.7.6 to 1.7.8 #55

Closed
wants to merge 1 commit into from

Conversation

kpango
Copy link
Contributor

@kpango kpango commented Oct 6, 2023

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


Snyk has created this PR to upgrade vald-client-node from 1.7.6 to 1.7.8.

ℹ️ 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 2 versions ahead of your current version.
  • The recommended version was released 21 days ago, on 2023-09-15.
Release notes
Package name: vald-client-node from vald-client-node GitHub release notes
Commit messages
Package name: vald-client-node

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

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@vankichi vankichi closed this Feb 15, 2024
@hlts2 hlts2 deleted the snyk-upgrade-5e29e3224a05504c03be74ee20f7b181 branch May 21, 2024 03:25
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.

4 participants