When testing an MU app, I realized that a few blueprints (controllers, helpers, initializers...) were not working; the reason is that the MU app blueprint has configured an old ember-source version.

    "ember-source": "https://s3.amazonaws.com/builds.emberjs.com/canary/shas/caa2c70d40dbfeffb0e6c9ac15ff6d72c8e24bae.tgz",

The latest ember-source upgrade for MU blueprint was done at #7976.

The mentioned blueprints are already working on the latest Ember release, then changing the ember-source version fixes the blueprints.

I wonder what is preventing from using the latest ember version with MU apps; I posted the question previously at #8085 (comment)

I think it may be better if MU apps use the latest Ember release:

• users testing MU could benefit from the latest changes (in my case, it was the Ember blueprints).
• users could report any existing issue against the latest stable version.

I can work on the PR, but I would like to know which strategy should follow at this moment:

• upgrade to a particular build
• use the latest release.

If the second option is decided, the MU blueprint should also be updated with each new Ember version as in a824605