3.4.5

Install

For the best developer experience and dependency management, install with Composer using the following command: composer create-project acquia/lightning-project MYPROJECT

Changelog

• Added support for Lightning Media 4.

Update steps

Update your codebase:

composer self-update
composer require acquia/lightning:~3.4.5 --no-update
composer update

Run database updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush updatedb

Run Lightning configuration updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush update:lightning

For general update instructions see https://gitub.com/acquia/lightning/blob/8.x-3.x/UPDATE.md.

5.0.0

Install

For the best developer experience and dependency management, install with Composer using the following command: composer create-project acquia/lightning-project MYPROJECT

Notes (important!)

• It is possible to update to this version of Lightning directly from version 3.4.x, OR from version 4.1.x. You do NOT need to update from 3.4.x TO 4.1.x in order to update to this version. However...
• You cannot update to Lightning 5 from Lightning 3.3.x, 4.0.x, or earlier. This is a limitation of Drupal core. You must be on Drupal 8.8 or 8.9 before you can update to Drupal 9. So, if you are on an old version of Lightning, now is a very good time to update to 3.4.x or 4.1.x, depending on which major version of Lightning you are currently using.
• Lightning 5 drops support for Drupal Console. The lightning:version command has been removed because Lightning now natively supports semantic versioning, and the lightning:subprofile command has been ported to Drush. To generate a sub-profile, run drush generate lightning-subprofile.
• Lightning 5 does not include the Libraries API module, because it will not be ported to Drupal 9. If you are using it, you will need to either copy or fork it into your project directly, or drop your usage of it. The most common usage of Libraries API -- finding the location of an asset library -- has been moved into core. See https://www.drupal.org/node/3099614 for more information.
• This release effectively deprecates Panelizer support in Lightning. Lightning 5 requires Panelizer 5, which implements a migration path to Layout Builder. You can do the migration at your own pace; in the interim, existing Panelizer layouts will continue to work, but default layouts will be read-only. More information is available at http://lightning.acquia.com/blog/how-migrate-panelizer-layout-builder.
• This release includes Lightning Media 4, which uses the core Media Library module instead of Entity Browser for certain things (Entity Browser is still used for image fields), and the core oEmbed system instead of Video Embed Field. Video Embed Field is still included to support existing sites, but will be removed as a dependency from Lightning Media 5. (Lightning Media will warn you about this.)

Changelog

• Updated Lightning API to 4.6:
  • Dropped support for Drupal 8.7.
  • Several internal infrastructure changes, but nothing that should affect users of Lightning API.
• Updated Lightning Media to 4.1:
  • Fixed bugs introduced in Lightning Media 4.0 that could occur when updating from very old versions of Lightning.
  • Deprecated the dependency on Views Infinite Scroll. It will NOT be included in Lightning Media 5.0, so if you need to continue using it in your project, you will need to add it to your composer.json. For example: composer require drupal/views_infinite_scroll:^1.6.
  • The image browser has been split into its own separate view, called "Image Browser". This change will not affect existing sites.
  • Lightning Media is now compatible with the Standard installation profile. Existing sites are unaffected by this change.
  • Fixed a bug where the link to bulk upload media would not show up on all displays of the administrative media library. (Issue #3155229)
• Updated Lightning Layout to 2.7:
  • Updated Simple GMap to 3.0.
  • Fixed a bug where new dependencies were not enabled during update. (Issue #3098556)

Update steps

Update your codebase:

composer self-update
composer require acquia/lightning:~5.0.0 --no-update
composer update

Run database updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush updatedb

Run Lightning configuration updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush update:lightning

For general update instructions see https://github.com/acquia/lightning/wiki/Update-Instructions.

5.0.0-beta3

Install

For the best developer experience and dependency management, install with Composer using the following command: composer create-project acquia/lightning-project MYPROJECT

Changelog

• Security updated Drupal core to 9.0.1.

Update steps

Update your codebase:

composer self-update
composer require acquia/lightning:~5.0.0-beta3 --no-update
composer update

Run database updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush updatedb

Run Lightning configuration updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush update:lightning

For general update instructions see https://github.com/acquia/lightning/blob/5.0.x/UPDATE.md.

4.1.5

Install

For the best developer experience and dependency management, install with Composer using the following command: composer create-project acquia/lightning-project MYPROJECT

Changelog

• Updated Lightning Layout to 2.6.
• Security updated Drupal core to 8.8.8.

Update steps

Update your codebase:

composer self-update
composer require acquia/lightning:~4.1.5 --no-update
composer update

Run database updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush updatedb

Run Lightning configuration updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush update:lightning

For general update instructions see https://github.com/acquia/lightning/blob/8.x-4.x/UPDATE.md.

3.4.4

Install

For the best developer experience and dependency management, install with Composer using the following command: composer create-project acquia/lightning-project MYPROJECT

Changelog

• Security updated Drupal core to 8.8.8.

Update steps

Update your codebase:

composer self-update
composer require acquia/lightning:~3.4.4 --no-update
composer update

Run database updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush updatedb

Run Lightning configuration updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush update:lightning

For general update instructions see https://gitub.com/acquia/lightning/blob/8.x-3.x/UPDATE.md.

5.0.0-beta2

Install

For the best developer experience and dependency management, install with Composer using the following command: composer create-project acquia/lightning-project MYPROJECT

Important Notes

See the release notes for Lightning 5.0.0-beta1 for important information about updating from earlier versions of Lightning.

Changelog

• Updated Search API to 1.17. Note that this release includes a backwards compatibility-breaking change; see https://www.drupal.org/node/3138575 for more information.
• Updated Page Manager to 4.0-beta6.

Update steps

Update your codebase:

composer self-update
composer require acquia/lightning:~5.0.0-beta2 --no-update
composer update

Run database updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush updatedb

Run Lightning configuration updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush update:lightning

For general update instructions see https://github.com/acquia/lightning/blob/5.0.x/UPDATE.md.

5.0.0-beta1

Install

For the best developer experience and dependency management, install with Composer using the following command: composer create-project acquia/lightning-project MYPROJECT

Notes (important!)

• It is possible to update to this version of Lightning directly from version 3.4.x, OR from version 4.1.x. You do NOT need to update from 3.4.x TO 4.1.x in order to update to this version. However...
• You cannot update to Lightning 5 from Lightning 3.3.x, 4.0.x, or earlier. This is a limitation of Drupal core. You must be on Drupal 8.8 or 8.9 before you can update to Drupal 9. So, if you are on an old version of Lightning, now is a very good time to update to 3.4.3 or 4.1.4, depending on which major version you are currently using.
• This release includes a development snapshot of the Search API module because the most recently released version does not support Drupal 9. Lightning 5.0.0's first stable release will include a tagged, Drupal 9-compatible release of Search API. If your site is not allowed to use development snapshots of contributed modules, hold off on updating to this version of Lightning.
• Lightning 5 drops support for Drupal Console. The lightning:version command has been removed because Lightning now natively supports semantic versioning, and the lightning:subprofile command has been ported to Drush. To generate a sub-profile, run drush generate lightning-subprofile.
• Lightning 5 does not include the Libraries API module, because it will not be ported to Drupal 9. If you are using it, you will need to either copy or fork it into your project directly, or drop your usage of it. The most common usage of Libraries API -- finding the location of an asset library -- has been moved into core. See https://www.drupal.org/node/3099614 for more information.
• This release effectively deprecates Panelizer support in Lightning. Lightning 5 requires Panelizer 5, which implements a migration path to Layout Builder. You can do the migration at your own pace; in the interim, existing Panelizer layouts will continue to work, but default layouts will be read-only. More information is available at http://lightning.acquia.com/blog/how-migrate-panelizer-layout-builder.
• This release includes Lightning Media 4, which uses the core Media Library module instead of Entity Browser for certain things (Entity Browser is still used for image fields), and the core oEmbed system instead of Video Embed Field. Video Embed Field is still included to support existing sites, but will be removed as a dependency from Lightning Media 5. (Lightning Media will warn you about this.)

Changelog

• Updated Drupal core to 9.0.0.
• Ported the lightning:subprofile Drupal Console command to Drush. To generate a sub-profile, run drush generate lightning-subprofile.
• Removed the lightning:version command. It is no longer needed because Lightning natively uses semantic versioning as of Lightning 5.0.0-alpha1.
• Added the Pendo module as a dependency.
• Updated Lightning Media to 4.0-beta1:
  • Lightning Media now uses the core Media Library module in place of the media browser by default. All media types packaged with Lightning Media now support the core Media Library module out of the box. Media Library is also now the default way of embedding media into WYSIWYG text editors, so Lightning Media no longer has a hard dependency on the Entity Embed module.
  • Lightning Media Video now uses the core oEmbed system by default and no longer has a hard dependency on the Video Embed Field module. Existing sites are not affected by this change.
  • Made the Document field required on the Document media type.
  • Updated the Slick Entity Reference module to 2.0.
  • Lightning Media no longer includes Libraries API as a dependency.
  • Updated DropzoneJS to 2.1.
  • Updated Entity Browser to 2.3.

Update steps

Update your codebase:

composer self-update
composer require acquia/lightning:~5.0.0-beta1 --no-update
composer update

Run database updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush updatedb

Run Lightning configuration updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush update:lightning

For general update instructions see https://github.com/acquia/lightning/blob/5.0.x/UPDATE.md.

4.1.4

Install

For the best developer experience and dependency management, install with Composer using the following command: composer create-project acquia/lightning-project MYPROJECT

Changelog

• Updated Lightning Core to 5.2:
  • Security updated Drupal core to 8.8.6.
• Ported the lightning:subprofile Drupal Console command to Drush. To generate a sub-profile,
  run drush generate lightning-subprofile.

Update steps

Update your codebase:

composer self-update
composer require acquia/lightning:~4.1.4 --no-update
composer update

Run database updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush updatedb

Run Lightning configuration updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush update:lightning

For general update instructions see https://github.com/acquia/lightning/blob/8.x-4.x/UPDATE.md.

3.4.3

Install

For the best developer experience and dependency management, install with Composer using the following command: composer create-project acquia/lightning-project MYPROJECT

Changelog

• Updated Lightning Core to 5.2:
  • Security updated Drupal core to 8.8.6.
• Ported the lightning:version Drupal Console command to Drush.
• Ported the lightning:subprofile' Drupal Console command to Drush. To generate a sub-profile, run drush generate lightning-subprofile`.

Update steps

Update your codebase:

composer self-update
composer require acquia/lightning:~3.4.3 --no-update
composer update

Run database updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush updatedb

Run Lightning configuration updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush update:lightning

For general update instructions see https://gitub.com/acquia/lightning/blob/8.x-3.x/UPDATE.md.

5.0.0-alpha1

Install

For the best developer experience and dependency management, install with Composer using the following command: composer create-project acquia/lightning-project MYPROJECT

Caveats

A few things to note about Lightning 5:

• This is an early alpha. It is NOT meant for production use! It's for you to test the Drupal 9 waters. As with all alpha releases, we do not guarantee an update path.
• Lightning 5 drops support for Drupal Console, in favor of Drush. Before we release a stable version, we will port the lightning:subprofile command to Drush.
• Lightning 5 does NOT include the Libraries API module, because it doesn't appear that it will support Drupal 9. If you are using it, you will need to copy or fork it into your own project directly, or drop your usage of it. (The most common use of Libraries API -- finding the location of an asset library -- has been moved into core. See https://www.drupal.org/node/3099614 for details.)
• This release effectively deprecates Panelizer support in Lightning. Lightning 5 requires Panelizer 5, which implements a migration to Layout Builder. You can do the migration on your own time; in the interim, existing Panelizer layouts will continue to work, but default layouts will be read-only. More details at http://lightning.acquia.com/blog/how-migrate-panelizer-layout-builder.
• This release includes a pre-release snapshot of Lightning Media 4, which uses the core Media Library module in place of Entity Browser for certain things (Entity Browser is still used for image fields), and the core oEmbed system instead of Video Embed Field. Video Embed Field is still included to support existing sites, but will be removed as a dependency from Lightning Media 4. (Lightning Media will trigger warnings about this.)
• You cannot update to Lightning 5 from Lightning 3.3.x, 4.0.x, or earlier. This is a limitation of Drupal core. You must be on Drupal 8.8 or 8.9 before you can upgrade to Drupal 9. So if you are on an old version of Lightning, now is a very good time to update to either 3.4.x or 4.1.x, depending on which major version you are currently using. (Note that you do NOT need to update from 3.4.x to 4.1.x in order to update to Lightning 5.)

Changelog

• Updated Drupal core to 9.0.0-beta2.
• Ported the lightning:version command to Drush.

Update steps

Update your codebase:

composer self-update
composer require acquia/lightning:~5.0.0-alpha1 --no-update
composer update

Run database updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush updatedb

Run Lightning configuration updates (if required - depending on the version from which you are updating):

drush cache:rebuild
drush update:lightning

For general update instructions see https://github.com/acquia/lightning/blob/5.0.x/UPDATE.md.