An in-range update of ember-cli is breaking the build 🚨

greenkeeper[bot] commented 6 years ago

Version 3.2.0 of ember-cli was just published.

Branch	Build failing 🚨
Dependency	ember-cli
Current Version	3.1.4
Type	devDependency

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

ember-cli 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

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/bmeurant/ember-array-contains-helper/builds/399302994?utm_source=github_status&utm_medium=notification) - ✅ **coverage/coveralls** First build on greenkeeper/ember-cli-3.2.0 at 96.296% [Details](https://coveralls.io/builds/17798506)

Release Notes

Deliverance

Setup

npm install -g ember-cli@3.2.0 -- Install new global ember-cli

Project Update

rm -rf node_modules dist tmp -- Delete temporary development folders.
npm install --save-dev ember-cli@3.2.0 -- Update project's package.json to use latest version.
npm install -- Reinstall NPM dependencies.
ember init -- This runs the new project blueprint on your projects directory. Please follow the prompts, and review all changes (tip: you can see a diff by pressing d). The most common source of upgrade pain is missing changes in this step.

Changelog

The following changes are required if you are upgrading from the previous
version:

Users
- ember new diff
- Upgrade your project's ember-cli version - docs
Addon Developers
- ember addon diff
Core Contributors
- No changes required

Community Contributions

#7560 Migrate to new format for mode specific arguments in testem config. @rwjblue
#7621 Take newer symlink-or-copy @ef4
#7698 Update ember-cli-qunit dependency @CodingItWrong
#7809 Do not attempt to compress server sent events. @rwjblue
#7811 replace TRAVIS with CI @kellyselden
#7833 blueprints/addon: Add yarn.lock file to .npmignore @Turbo87
#7836 tests: Increase timeout for linting tests @Turbo87
#7857 Filter out blacklisted addons before calling included hook @dnachev
#7880 testem: Improve Chrome command line flags @stefanpenner

Thank you to all who took the time to contribute!

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 6 years ago

After pinning to 3.1.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 6 years ago

Version 3.3.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

Believer

Setup

npm install -g ember-cli@3.3.0 -- Install new global ember-cli

Project Update

rm -rf node_modules dist tmp -- Delete temporary development folders.
npm install --save-dev ember-cli@3.3.0 -- Update project's package.json to use latest version.
npm install -- Reinstall NPM dependencies.
npm install -g ember-cli-update -- Install Ember CLI update tool globally.
ember-cli-update -- This will update your app or addon to the latest Ember CLI version. You will probably encounter merge conflicts, in which the default behavior is to let you resolve conflicts on your own. You can supply the --resolve-conflicts option to run your system's git merge tool if any conflicts are found.