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 strong-error-handler to the latest version 🚀 #22

Merged
merged 1 commit into from
Jul 25, 2017

Conversation

greenkeeper[bot]
Copy link

@greenkeeper greenkeeper bot commented Jul 20, 2017

Version 2.2.0 of strong-error-handler just got published.

Dependency strong-error-handler
Current Version 2.1.0
Type devDependency

The version 2.2.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of strong-error-handler.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


Commits

The new version differs by 3 commits.

  • 3bf59a7 2.2.0
  • 68e0aa5 Merge pull request #55 from charanrajtc/added-response-format-option
  • 4d97392 Add new option: negotiateContentType

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

@coveralls
Copy link

Coverage Status

Coverage remained the same at 82.178% when pulling 0b17f03 on greenkeeper/strong-error-handler-2.2.0 into e3e97cd on master.

@mrfelton mrfelton merged commit 0b17f03 into master Jul 25, 2017
@greenkeeper greenkeeper bot deleted the greenkeeper/strong-error-handler-2.2.0 branch July 25, 2017 07:05
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.

2 participants