An in-range update of connect-redis is breaking the build 🚨
- 主要言語
- 言語のデータがありません
- スター
- 3
- フォーク
- 1
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
## The dependency [connect-redis](https://github.com/visionmedia/connect-redis) was updated from `3.4.1` to `3.4.2`.
🚨 [View failing branch](https://github.com/aethant/merino/compare/master...aethant:greenkeeper%2Fconnect-redis-3.4.2).
This version is **covered** by your **current version range** and after updating it in your project **the build failed**.
connect-redis 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 failed ([Details](https://travis-ci.org/aethant/merino/builds/561024985?utm_source=github_status&utm_medium=notification)).
---
Commits
The new version differs by 4 commits.
5469fcbv3.4.23609797Fix compatibility issues with ioredis + Clustera2babdaBump devDependenciese8744e4Session check verbiage reduction
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](https://greenkeeper.io) Bot :palm_tree:
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
Start by reproducing the failure on the Greenkeeper connect-redis 3.4.2 branch and inspect the Travis CI build linked in the issue. Compare the four listed connect-redis commits with the project's dependency configuration, then verify that the build passes with a compatible dependency version.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- node.js, redis
- 領域
- backend, databases
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100