watson-developer-cloud / botkit-middleware

A middleware to connect Watson Conversation Service to different chat channels using Botkit
https://www.npmjs.com/package/botkit-middleware-watson
Apache License 2.0
207 stars 255 forks source link

An in-range update of ibm-watson is breaking the build 🚨 #176

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency ibm-watson was updated from 4.0.2 to 4.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ibm-watson is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/watson-developer-cloud/botkit-middleware/builds/526057492?utm_source=github_status&utm_medium=notification)).

Release Notes for v4.1.0

4.1.0 (2019-04-29)

Features

  • example: add speech-to-text-to-redis example (238cec3)
Commits

The new version differs by 7 commits.

  • 5c62db1 chore(release): 4.1.0 [skip ci]
  • d8b1666 docs: Add speech-to-text-to-redis example (#871)
  • 238cec3 feat(example): add speech-to-text-to-redis example
  • 71a0714 test: fix assistant v2 test
  • b149671 Merge pull request #868 from MasterOdin/skip_tests
  • a385669 test: wrap compare_comply integration tests in describe block
  • 3d78728 test: fix skipping two integration tests without auth.js

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

After pinning to 4.0.2 your tests are passing again. Downgrade this dependency πŸ“Œ.

germanattanasio commented 5 years ago

Fixed in 2.0.0