Skip to content

Update kube-probe to the latest version 🚀 #66

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

Merged
merged 2 commits into from
Feb 6, 2018

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Feb 5, 2018

Version 0.3.0 of kube-probe was just published.

Dependency kube-probe
Current Version 0.2.0
Type dependency

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.


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 🌴

@ghost ghost added the in progress label Feb 5, 2018
@ghost ghost assigned lholmquist Feb 5, 2018
@coveralls
Copy link

coveralls commented Feb 5, 2018

Coverage Status

Coverage remained the same at 96.825% when pulling 327093a on greenkeeper/kube-probe-0.3.0 into 0429834 on master.

@lholmquist lholmquist merged commit 85ec4b2 into master Feb 6, 2018
@ghost ghost removed the in progress label Feb 6, 2018
@greenkeeper greenkeeper bot deleted the greenkeeper/kube-probe-0.3.0 branch February 6, 2018 13:16
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.

3 participants