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

Update fluent-openapi to the latest version 🚀 #311

Merged
merged 1 commit into from
Aug 27, 2018

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Aug 27, 2018

Version 0.1.1 of fluent-openapi was just published.

Dependency fluent-openapi
Current Version 0.1.0
Type dependency

The version 0.1.1 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 fluent-openapi.

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 2 commits.

  • 175fa4c chore(release): 0.1.1
  • eec8ea7 refactor(client): remove some application specific client code

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 🌴

@silasbw silasbw merged commit 50ac41f into master Aug 27, 2018
@silasbw silasbw deleted the greenkeeper/fluent-openapi-0.1.1 branch August 27, 2018 23:19
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.

None yet

1 participant