Open greenkeeper[bot] opened 6 years ago
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.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.13.2
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.13.2
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!
Version 2.16.0 of ember-cli was just published.
The version 2.16.0 is not covered by your current version range.
If you donโt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of ember-cli.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donโt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
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: