Skip to content

[Snyk] Upgrade @kubernetes/client-node from 0.14.1 to 0.14.3 - #395

Merged
rfelber merged 1 commit into
mainfrom
snyk-upgrade-0d51b6ffa05fb6a449f79b6a1aba128d
May 2, 2021
Merged

rfelber merged 1 commit into
mainfrom
snyk-upgrade-0d51b6ffa05fb6a449f79b6a1aba128d

Conversation

@snyk-bot

@snyk-bot snyk-bot commented May 2, 2021

Copy link
Copy Markdown
Contributor

Snyk has created this PR to upgrade @kubernetes/client-node from 0.14.1 to 0.14.3.

merge advice
ℹ️ 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 2021-04-11.
Release notes
Package name: @kubernetes/client-node
  • 0.14.3 - 2021-04-11

    Update to version 0.14.2

  • 0.14.2 - 2021-04-08

    bump setup-node to v2

  • 0.14.1 - 2021-04-02

    Add a unit test to require registry.npm.js as the package registry.

from @kubernetes/client-node GitHub release notes
Commit messages
Package name: @kubernetes/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

@rfelber rfelber added the dependencies Pull requests that update a dependency file label May 2, 2021
@rfelber rfelber added this to the v2.7.0 milestone May 2, 2021
@rfelber rfelber self-assigned this May 2, 2021
@rfelber
rfelber merged commit 7fdf8c2 into main May 2, 2021
@rfelber
rfelber deleted the snyk-upgrade-0d51b6ffa05fb6a449f79b6a1aba128d branch May 2, 2021 22:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants