search

kellyselden / ember-cli-tree-shaker

Experiment with tree-shaking in Ember CLI
MIT License
76 stars 7 forks source link

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

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 3.1.3 of ember-cli was just published.

Branch Build failing 🚨
Dependency ember-cli
Current Version 3.1.2
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/kellyselden/ember-cli-tree-shaker/builds/373014450?utm_source=github_status&utm_medium=notification)
Release Notes Greenprints

Setup

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

Project Update

  1. rm -rf node_modules dist tmp -- Delete temporary development folders.
  2. npm install --save-dev ember-cli@3.1.3 -- Update project's package.json to use latest version.
  3. npm install -- Reinstall NPM dependencies.
  4. 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:

Community Contributions

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.2 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.1.4 just got published.

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