Release 2.0.0

💥 Breaking Change

• #521 [Breaking] Switch to Github Actions for CI (@jrjohnson) - The breaking change here is that we have dropped support for Node 12.

🐛 Bug Fix

• #535 Fix plugin name extraction for scoped packages (@astronomersiva)

📝 Documentation

• #530 Update package search links in docs since npmsearch.com is no longer registered (@lukemelia)

🏠 Internal

• #529 Update CI badge in README and use volta in CI (@lukemelia)

Committers: 14

• Alon Bukai (@Alonski)
• Andrii Vakarev (@avakarev)
• Bruno Casali (@brunoocasali)
• Camille TJHOA (@ctjhoa)
• Deepan Subbiah (@deepan83)
• Jon Johnson (@jrjohnson)
• Karl Becker (@karlbecker)
• Kelly Selden (@kellyselden)
• Luke Melia (@lukemelia)
• Olle Jonsson (@olleolleolle)
• Peter Lejeck (@NuckChorris)
• Simon Ihmig (@simonihmig)
• Sivasubramanyam A (@astronomersiva)
• @akashdsouza

Spaced out

• Only emit plugin message if none are present #487 @dfreeeman

L'avenir

Full Changelog

• Fix syntax for aliasing plugins #467 @calvinlough
• Tolerate other names than those starting with ember-cli-deploy #469 @duizendnegen

Uno

Although ember-cli-deploy has had a fairly stable API since 0.5.x, this 1.0.0 release signifies that we are committed to supporting this API through the 1.x series, in accordance with SemVer.

Since 0.6.x, we have deprecated the plugins config option in favor of a more flexible and expressive approach.

Thanks to the efforts of @ef4 and @achambers the plugin ordering/disable/aliasing strategy has been entirely rewritten (originally released in 1.0.0-beta.1):

• the user can disable individual plugins by setting disabled: {pluginName: true} on each plugin's config entry.
• the user can disable all plugins except some using disable: {allExcept: ['plugin1', 'plugin2']}
• the user can influence plugin order by expressing inter-plugin dependencies with runBefore and runAfter on each plugin's config entry.
• plugin authors can influence plugin order by expressing inter-plugin dependencies by setting runBefore and runAfter properties directly on their plugin instance.
• plugin aliasing is now done by setting alias: {original: ['alias1', 'alias2']}

To get more information go visit the Ember CLI Deploy website

Upgrade notes are also available here

Plugin authors, if your plugin worked under 0.6, it will work under 1.0 with no changes needed.

The Process

We anticipate this pre-release being the last beta before 1.0.0. If you try it out on your app and let us know about any issues you run into, your contribution will be rewarded with great appreciation and karma.

There are no API changes in this beta. (Note that the previous beta deprecated the plugins config option in favor of a more flexible and expressive approach. See beta.1 release notes for details).

Changes in this beta consist of updated and trimmed dependencies, including the elimination of dependencies on ember-cli internals. Thanks to @duizendnegen for his work on this front.

To get more information go visit the Ember CLI Deploy website

Upgrade notes are also available here

Road to Rio

This pre-release has no breaking changes from 0.6.4 but deprecates the old way of specifying the plugins config property.

Thanks to the efforts of @ef4 and @achambers the plugin ordering/disable/aliasing strategy has been entirely rewritten:

• the user can disable individual plugins by setting disabled: {pluginName: true} on each plugin's config entry.
• the user can disable all plugins except some using disable: {allExcept: ['plugin1', 'plugin2']}
• the user can influence plugin order by expressing inter-plugin dependencies with runBefore and runAfter on each plugin's config entry.
• plugin authors can influence plugin order by expressing inter-plugin dependencies by setting runBefore and runAfter properties directly on their plugin instance.
• plugin aliasing is now done by setting alias: {original: ['alias1', 'alias2']}

To get more information go visit the Ember CLI Deploy website

Upgrade notes are also available here

Pull Request

Remains of the Day

• Fix CoreObject init/super deprecation #410 (alisdair)
• add support for requiredHooks in pipelines for better error messages #406 (ghedamat)
• Validate configured plugins before continue with pipeline #405 (zzarcon)

Remote Nation

• #402 Fix plugin context merging in the pipeline model @dannyfallon/df

Two If By Sea

• Bump lodash version to remove warning #388 @orf
• Update ember-cli links to ember-cli-deploy #392 @yothomas

Passement

This release fixes a regression introduced by 0.6.0 that caused the command line flag for specifying a config file to stop working. Thanks to @dschmidt for the fix.

This release also adds config options for specifying log colors (some users had complaints about lack of contrast against certain terminal backgrounds). Documentation is still forthcoming on this feature, but you can check PR #377 if you're anxious to use this.

Pull Requests:

• Fix config file option #385 (dschmidt)
• add config options for log colors #377 (ghedamat)