The version 2.12.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of ember-cli.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notesle train à paris
Setup
npm uninstall -g ember-cli -- Remove old global ember-cli
npm cache clean -- Clear NPM cache
bower cache clean -- Clear Bower cache
npm install -g ember-cli@2.12.0 -- Install new global ember-cli
npm install --save-dev ember-cli@2.12.0 -- Update project's package.json to use latest version.
npm install -- Reinstall NPM dependencies.
bower install -- Reinstall bower 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:
#6860 blueprints/app: Update "ember-source" and "ember-data" to v2.12.0 @Turbo87
Thank you to all who took the time to contribute!
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 2.12.0 of ember-cli just got published.
The version 2.12.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of ember-cli. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
le train à parisSetup
npm uninstall -g ember-cli
-- Remove old global ember-clinpm cache clean
-- Clear NPM cachebower cache clean
-- Clear Bower cachenpm install -g ember-cli@2.12.0
-- Install new global ember-cliProject Update
rm -rf node_modules bower_components dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.12.0
-- Update project'spackage.json
to use latest version.npm install
-- Reinstall NPM dependencies.bower install
-- Reinstall bower 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:
ember new
diffember addon
diffCommunity Contributions
preprocessTree
/postprocessTree
for addons. @rwjbluebroccoli-babel-transpiler
. @rwjblueinit
instrumentation. @ember-clibeforeRun
is included incommand
instrumentation. @rwjbluevar
. @rwjblueTask.prototype.run
returns promises @ember-clibower.json
from default blueprints. @rwjblue_shouldCompileJS
to guard precompilation of addon JS. @rwjblueamd
for transpiling modules with babel@5. @ember-cliamd
for transpiling modules with babel@5." @ember-cliThank you to all who took the time to contribute!
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: