An in-range update of coveralls is breaking the build 🚨

## The devDependency [coveralls](https://github.com/nickmerwin/node-coveralls) was updated from `3.0.2` to `3.0.3`.

🚨 [View failing branch](https://github.com/code-corps/code-corps-ember/compare/develop...code-corps:greenkeeper%2Fcoveralls-3.0.3).

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

coveralls is a devDependency of this project. It **might not break your production code or affect downstream projects**, but probably breaks your build or test tools, which may **prevent deploying or publishing**.

Status Details

- ❌ **ci/circleci: build:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/code-corps/code-corps-ember/7942?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).

---

Release Notes for Dependency security updates

As suggested by NPM and Snyk.

Commits

The new version differs by 1 commits.

• aa2519c dependency security audit fixes from npm & snyk (#210)

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:

先檢查 coveralls 從 3.0.2 到 3.0.3 的更新以及連結的失敗分支，然後檢查 CircleCI 建置詳細資訊，以找出失敗的步驟。當相依性更新不再破壞建置，且相關的 CI 檢查通過時，工作即完成。

由索引模型根據 Issue 內容生成。