This repository was archived by the owner on Feb 2, 2021. It is now read-only.
Update kube-probe to the latest version 🚀 #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=80&v=4){kind=small}
ghost
added
the
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 0.3.0 of kube-probe was just published.
The version 0.3.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of kube-probe.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 11 commits.
de0783c0.3.03200472Merge pull request #30 from lance/overload-protection9d8fd42doc: update README.md with overload-protection infof7bdc7esrc: merge user overload protection options3d8e721src: reduce code duplicationcc7693dfeat: add overload protection to the readiness and liveness endpointsa192093Update eslint to the latest version 🚀 (#28)65164faUpdate eslint-plugin-node to the latest version 🚀 (#29)4a0482fUpdate eslint-plugin-react to the latest version 🚀 (#27)c1919ffUpdate eslint to the latest version 🚀 (#26)ad425d8Update eslint to the latest version 🚀 (#25)See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴