🚨🔥⚠️ 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 covered by your current version range and after updating it in your project the build went from success to failure.
As ember-cli is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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 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.
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.12.3.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As ember-cli is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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 cachebower cache clean-- Clear Bower cachenpm install -g ember-cli@2.12.3-- 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.3-- Update project'spackage.jsonto 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 newdiffember addondiffCommunity Contributions
Thank you to all who took the time to contribute!