Open greenkeeper[bot] opened 7 years ago
Update to this version instead 🚀
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-clirm -rf node_modules bower_components dist tmp
-- Delete temporary development folders.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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffpreprocessTree
/ postprocessTree
for addons. @rwjbluebroccoli-babel-transpiler
. @rwjblueinit
instrumentation. @ember-clibeforeRun
is included in command
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!
Update to this version instead 🚀
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.1
-- Install new global ember-clirm -rf node_modules bower_components dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.12.1
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
difftreeForAddon
around addon/**/*.js
files. @rwjblueThank you to all who took the time to contribute!
Update to this version instead 🚀
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.2
-- Install new global ember-clirm -rf node_modules bower_components dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.12.2
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffThank you to all who took the time to contribute!
Update to this version instead 🚀
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.3
-- Install new global ember-clirm -rf node_modules bower_components dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.12.3
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffThank you to all who took the time to contribute!
Update to this version instead 🚀
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.13.0
-- Install new global ember-clirm -rf node_modules bower_components dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.13.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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffThank you to all who took the time to contribute!
Update to this version instead 🚀
npm uninstall -g ember-cli
-- Remove old global ember-clinpm cache clean
-- Clear NPM cachenpm install -g ember-cli@2.13.1
-- Install new global ember-clirm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.13.1
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffnpm install foo
to yarn install foo
@Turbo87Thank you to all who took the time to contribute!
Update to this version instead 🚀
npm uninstall -g ember-cli
-- Remove old global ember-clinpm cache clean
-- Clear NPM cachenpm install -g ember-cli@2.13.2
-- Install new global ember-clirm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.13.2
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
difflintTree
results cannot clobber tests. @rwjblueThank you to all who took the time to contribute!
Update to this version instead 🚀
npm uninstall -g ember-cli
-- Remove old global ember-clinpm cache clean
-- Clear NPM cachenpm install -g ember-cli@2.14.0
-- Install new global ember-clirm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.14.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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffnew
and init
so that it can be skipped with --no-welcome @romulomachadoyarn install
when yarn.lock file is present @samdemaeyerit
@sduquejnpm install foo
to yarn install foo
@pichflchalk.white
when displaying asset sizes @lucasmazzaaddon.app
is set. @stefanpennerThank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@2.14.2
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.14.2
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffThank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@2.15.0
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.15.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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffamd-name-resolver
version to enable parallel babel transpile @mikrostewThank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@2.16.1
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.16.1
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffThank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@2.16.2
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.16.2
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffThank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@2.17.0
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.17.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.The following changes are required if you are upgrading from the previous
version:
ember new
diffundefined
values in merged aliases @twokulapp/
directory. @rwjblueuseYarn
flag if necessary @Turbo87ember-cli-shims
to v1.2.0 @Turbo87Thank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@2.17.2
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.17.2
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffember new --yarn
not using yarn @Turbo87Thank you to all who took the time to contribute!
Update to this version instead 🚀
The following changes are required if you are upgrading from the previous
version:
ember new
diffember new --yarn
not using yarn @Turbo87separator: '\n;'
to vendor JS concat @kellyselden/lennyuseYarn
from constructor args @lennyburdetteoverrides
for a single .eslintrc.js
. @rwjblueensureDir
to avoid race condition in mk-tmp-dir-in
. @rwjblueblueprints/app/files/package.json
. @rwjblueThank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@2.18.1
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@2.18.1
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffThank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@3.1.0
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@3.1.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.The following changes are required if you are upgrading from the previous
version:
ember new
diffcontentFor()
hooks"Thank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@3.1.1
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@3.1.1
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffThank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@3.1.2
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@3.1.2
-- 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.The following changes are required if you are upgrading from the previous version:
ember new
diffThank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@3.1.3
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.npm install --save-dev ember-cli@3.1.3
-- 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.The following changes are required if you are upgrading from the previous
version:
ember new
diffThank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@3.2.0
-- Install new global ember-cli
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.The following changes are required if you are upgrading from the previous
version:
ember new
diffember-cli-qunit
dependency @CodingItWrongyarn.lock
file to .npmignore
@Turbo87Thank you to all who took the time to contribute!
Update to this version instead 🚀
npm install -g ember-cli@3.3.0
-- Install new global ember-cli
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.The following changes are required if you are upgrading from the previous
version:
ember new
diffdevDependency
ember-cli was updated from 2.10.0
to 3.4.2
.Update to this version instead 🚀
npm install -g ember-cli@NEW_VERSION_NUMBER
-- Install new global ember-cli
Project Update
rm -rf node_modules dist tmp
-- Delete temporary development folders.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 release. You will probably encounter merge conflicts that you should resolve in your normal git
workflow.ember-cli-update --run-codemods
- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features.The following changes are required if you are upgrading from the previous
version:
ember new
diffember addon
diffstyles
behaviour @twokulThank you to all who took the time to contribute!
devDependency
ember-cli was updated from 2.10.0
to 3.4.3
.Update to this version instead 🚀
npm install -g ember-cli@3.4.3
-- Install new global ember-cli
Project Update
rm -rf node_modules dist tmp
-- Delete temporary development folders.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 release. You will probably encounter merge conflicts that you should resolve in your normal git
workflow.ember-cli-update --run-codemods
- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features.The following changes are required if you are upgrading from the previous
version:
ember new
diffember new
difftests
folder is not present @twokulapp.import
transforms for tests @twokulThank you to all who took the time to contribute!
devDependency
ember-cli was updated from 2.10.0
to 3.5.0
.Update to this version instead 🚀
npm install -g ember-cli@NEW_VERSION_NUMBER
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.ember-cli-update
- This will update your app or addon to the latest ember-cli release. You will probably encounter merge conflicts that you should resolve in your normal git workflow.ember-cli-update --run-codemods
- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features.yarn.lock
to .npmignore
@Turbo87qunit-dom
to v0.8.0 @Turbo87--in
option to ember generate
and ember destroy
to allow blueprint generation for in repo addons in custom paths. @scalvertpublic
to the list of disallowed application names @twokulThank you to all who took the time to contribute!
devDependency
ember-cli was updated from 2.10.0
to 3.5.1
.Update to this version instead 🚀
npm install -g ember-cli@3.5.1
-- Install new global ember-cli
rm -rf node_modules dist tmp
-- Delete temporary development folders.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 release. You will probably encounter merge conflicts that you should resolve in your normal git workflow.ember-cli-update --run-codemods
-- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features.debug
for package-info-cache
messages @stefanpennertoTree()
with custom paths @wagenetThank you to all who took the time to contribute!
devDependency
ember-cli was updated from 2.10.0
to 3.6.0
.Update to this version instead 🚀
npm install -g ember-cli@3.6.0
-- Install new global ember-cli
npx ember-cli-update --to 3.6.0
-- This will update your app or addon to the latest ember-cli release. You will probably encounter merge conflicts that you should resolve in your normal git workflow.npx ember-cli-update --run-codemods
-- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features.package-info-cache
warnings under DEBUG
control @dcombslinkedinREADME
to CONTRIBUTING
@kennethlarsen/feature.jshintrc
and .eslintrc
when generating lib
or packages
@ppcano--ssl
options to ember test
@nathanhammondaddon-test-support
out of the tests
folder @Turbo87Thank you to all who took the time to contribute!
devDependency
ember-cli was updated from 2.10.0
to 3.6.1
.Update to this version instead 🚀
npm install -g ember-cli@3.6.1
-- Install new global ember-cli
npx ember-cli-update --to 3.6.1
-- This will update your app or addon to the latest ember-cli release. You will probably encounter merge conflicts that you should resolve in your normal git workflow.npx ember-cli-update --run-codemods
-- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features.ember-default
scenario to ember-try
config again @bendemboskiThank you to all who took the time to contribute!
devDependency
ember-cli was updated from 2.10.0
to 3.7.0
.Update to this version instead 🚀
npm install -g ember-cli@3.7.0
-- Install new global ember-cli
npx ember-cli-update --to 3.7.0
-- This will update your app or addon to the latest ember-cli release. You will probably encounter merge conflicts that you should resolve in your normal git workflow.npx ember-cli-update --run-codemods
-- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features.relative-module-paths
caching @Turbo87Thank you to all who took the time to contribute!
devDependency
ember-cli was updated from 2.10.0
to 3.7.1
.Update to this version instead 🚀
npm install -g ember-cli@3.7.1
-- Install new global ember-cli
npx ember-cli-update --to 3.7.1
-- This will update your app or addon to the latest ember-cli release. You will probably encounter merge conflicts that you should resolve in your normal git workflow.npx ember-cli-update --run-codemods
-- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features..travis.yml
config @buschtoensThank you to all who took the time to contribute!
devDependency
ember-cli was updated from 2.10.0
to 3.8.0
.Update to this version instead 🚀
npm install -g ember-cli@3.8.0
-- Install new global ember-cli
npx ember-cli-update --to 3.8.0
-- This will update your app or addon to the latest ember-cli release. You will probably encounter merge conflicts that you should resolve in your normal git workflow.npx ember-cli-update --run-codemods
-- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features.tests
directory when tests are disabled @f1sherman{{content-for}}
@mpiriofixturify
to devDependencies
@Turbo87exists-sync
dependency declaration @Turbo87ember-cli
entry file @Turbo87ember-cli-dependency-checker
to v3.1.0 @Turbo87ember-source
version for MU blueprints @ppcanoThank you to all who took the time to contribute!
devDependency
ember-cli was updated from 2.10.0
to 3.8.1
.Update to this version instead 🚀
npm install -g ember-cli@3.8.1
-- Install new global ember-cli
npx ember-cli-update --to 3.8.1
-- This will update your app or addon to the latest ember-cli release. You will probably encounter merge conflicts that you should resolve in your normal git workflow.npx ember-cli-update --run-codemods
-- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features.Thank you to all who took the time to contribute!
devDependency
ember-cli was updated from 2.10.0
to 3.8.2
.Update to this version instead 🚀
npm install -g ember-cli@3.8.2
-- Install new global ember-cli
npx ember-cli-update --to 3.8.2
-- This will update your app or addon to the latest ember-cli release. You will probably encounter merge conflicts that you should resolve in your normal git workflow.npx ember-cli-update --run-codemods
-- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features.ember-ajax
in blueprints and tests @boris-petrovmoduleName()
for templates @pzuraqThank you to all who took the time to contribute!
devDependency
ember-cli was updated from 2.10.0
to 3.9.0
.devDependency
ember-cli was updated from 2.10.0
to 3.10.0
.devDependency
ember-cli was updated from 2.10.0
to 3.10.1
.devDependency
ember-cli was updated from 2.10.0
to 3.11.0
.
Version 2.11.1 of ember-cli just got published.
The version 2.11.1 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.
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: