🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
npm uninstall -g ember-cli -- Remove old global ember-cli
npm cache clean -- Clear NPM cache
npm install -g ember-cli@2.13.1 -- Install new global ember-cli
Project Update
rm -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.
Changelog
The following changes are required if you are upgrading from the previous
version:
Hello lovely humans,
ember-cli just published its new version 2.13.1.
This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
Setup
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-cliProject Update
rm -rf node_modules dist tmp-- Delete temporary development folders.npm install --save-dev ember-cli@2.13.1-- Update project'spackage.jsonto 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:
ember newdiffember addondiffCommunity Contributions
npm install footoyarn install foo@Turbo87Thank you to all who took the time to contribute!