/ember-cli

Latest release
Verified
This commit was signed with a verified signature.
@rwjblue rwjblue Robert Jackson
GPG key ID: C900A17F29A78FDF Learn about signing commits
something something sassy
Latest release

@rwjblue rwjblue released this Sep 12, 2018 · 136 commits to master since this release

Assets 2

Setup

npm install -g ember-cli@3.4.2 -- Install new global ember-cli

Project Update

  1. rm -rf node_modules dist tmp -- Delete temporary development folders.
  2. npm install -g ember-cli-update -- Install Ember CLI update tool globally.
  3. Run 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.
  4. Run 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.

CHANGELOG

The following changes are required if you are upgrading from the previous
version:

Community Contributions

Thank you to all who took the time to contribute!

Pre-release
Galvanize
Pre-release

@twokul twokul released this Sep 10, 2018 · 140 commits to master since this release

Assets 3

Setup

npm install -g ember-cli@3.4.2-beta.1 -- Install new global ember-cli

Project Update

  1. rm -rf node_modules dist tmp -- Delete temporary development folders.
  2. npm install -g ember-cli-update -- Install Ember CLI update tool globally.
  3. 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.

Changelog

The following changes are required if you are upgrading from the previous
version:

  • Users
    • Upgrade your project's ember-cli version - docs
  • Addon Developers
    • No changes required
  • Core Contributors
    • No changes required

Community Contributions

Thank you to all who took the time to contribute!

Feels Like Summer

@twokul twokul released this Sep 6, 2018 · 145 commits to master since this release

Assets 3

Setup

npm install -g ember-cli@3.4.1 -- Install new global ember-cli

Project Update

  1. rm -rf node_modules dist tmp -- Delete temporary development folders.
  2. npm install --save-dev ember-cli@3.4.1 -- Update project's package.json to use latest version.
  3. npm install -- Reinstall NPM dependencies.
  4. npm install -g ember-cli-update -- Install Ember CLI update tool globally.
  5. 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.

Changelog

The following changes are required if you are upgrading from the previous version:

Community Contributions

Quick note about ember-cli@3.4.0: it was unpublished from NPM because the published tar file contained a
bug. NPM is write-only (that is you can unpublish a package but you cannot re-publish it with the same version) and that leaves us with only one option: publish a new version. We effectively fast-forwarded to 3.4.1.

Pre-release
Verified
This commit was signed with a verified signature.
@rwjblue rwjblue Robert Jackson
GPG key ID: C900A17F29A78FDF Learn about signing commits
Don't look at the dogs, work the lock....
Pre-release

@rwjblue rwjblue released this Aug 3, 2018 · 193 commits to master since this release

Assets 2

Setup

npm install -g ember-cli@3.4.0-beta.2 -- Install new global ember-cli

Project Update

  1. rm -rf node_modules dist tmp -- Delete temporary development folders.
  2. npm install -g ember-cli-update -- Install Ember CLI update tool globally.
  3. 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.

Changelog

The following changes are required if you are upgrading from the previous
version:

Community Contributions

  • #7902 add .eslintignore to .npmignore @kellyselden
  • #7904 further unify all our .*ignore files @kellyselden
  • #7905 Fix release branch tests @kellyselden
  • #7917 Adding entries for the package-info-cache work to the contribution list @dcombslinkedin
  • #7940 Enable LiveReload and normal app server to share a single port. @SparshithNR
  • #7947 Adding support for in repo addons in non-conventional directories @scalvert
  • #7949 Upgrade blueprint dependency versions @stefanpenner
  • #7950 Better handle ambiguity between package.json and index.js name field. @rwjblue
    • Changes the addon blueprint to ensure name property just references the package.json's name
    • Introduce a hard error when locally developing an addon whose package.json name differs from index.js name.
    • Updates Project.prototype.findAddonByName / Addon.prototype.findAddonByName to handle the changes to mentioned above. Specifically, findAddonByName will prefer exact matches to the package.json name over exact matches in index.js name.
  • #7954 Add template linting. @rwjblue
  • #7956 Embrace stages in CI. @rwjblue

Thank you to all who took the time to contribute!