Does anyone know why there is no canary tag for Ember?
npm view ember-source dist-tags
Yeah canary is just ‘master’. From the builds doc:
Ember releases follow a “train” release model. Every six weeks, the master branch of Ember (sometimes referred to as “canary”) branches to become the new beta. After six weeks as a beta, this version becomes the new stable release of Ember.
Should we use ember-master then in ember-try?
https://github.com/pouchdb-community/ember-pouch/commit/d9fc5569098c9676eaa3b0476484e7e83ec209cb
Think so. Anytime I’ve used Ember or Ember Data canary I’ve always just used #master branch so and I’m pretty sure that’s the recommended way to use canary. Someone a little more knowledgeable might be able to confirm…
Does this mean that ember-try should switch from NPM to the GitHub repository for the canary tests based on "repository": in the package.json ?
That will not work, as the master branch does not include the built artifacts for ember-source. Bower is fine.
We don’t use bower anymore, See GitHub - pouchdb-community/ember-pouch: PouchDB/CouchDB adapter for Ember Data
Then you can’t test against Ember release, beta, or canary. 
The default addon blueprint is setup to correctly test these channels (still via bower even though the addon normally does not use/need bower). You should model your config/ember-try.js around the default blueprint generated one.
release and beta work fine. See Travis CI - Test and Deploy Your Code with Confidence it is canary we also like to test.
Thanks! We found it. You can write ‘ember-source’: ‘components/ember#canary’ to enable canary testing using NPM.
https://github.com/pouchdb-community/ember-pouch/commit/3ad86a6ada0c075b22a6f4dc3749fe5153203714
FWIW, testing against canary without bower is now quite straightforward.
Canary - Releases - Ember.js contains the current instructions…
# Install the latest Ember canary:
npm install --save-dev <dynamic path to current build>.tgz
Thanks for this feedback and solving this!