2.1.7

2.1.6 to 2.1.7 Manual Update Steps

• IMPORTANT! Page Manager is no longer a dependency of Lightning Layout,
  and it will no longer ship with Lightning as of the next release. Therefore,
  if you are actively using Page Manager, you must add it to your project as an
  explicit dependency in order to continue to using it. Otherwise, you must
  uninstall it before updating to the next version of Lightning, or your site
  may break.
• IMPORTANT! Lightning has added support for pulling front-end JavaScript
  libraries into your project using Composer, via Asset Packagist.
  This requires a few simple, one-time changes to your project's root
  composer.json. Note that, without these changes, some functionality in
  future Lightning releases will not work. The required changes, and
  instructions on how to make them (either manually, or automatically using a
  Lightning-provided script) are documented here.
• Lightning now supports exposing all Drupal entities as JSON, in the standard
  JSON API format. To enable this feature, install the Content API module from
  the Lightning package.
• If Lightning's content role functionality is available, grant all "creator"
  content roles the following permissions, as desired:
  • Toolbar: Use the administration toolbar
  • Quick Edit: Access in-place editing
  • Contextual Links: Use contextual links

Changelog

• Security updated Drupal core to 8.3.7.
• Updated Entity Browser to 1.1.
• Lightning has a new top-level component called Content API. This component is installed by default and exposes all entities in your site in the machine-consumable JSON API format. This makes Lightning friendlier to decoupled applications, and allows it to be used as a backend for such. As part of this feature, Lightning now includes the JSON API, OpenAPI, and Simple OAuth modules, with basic default configuration. (GitHub #423, #421, #424, #433, and Issue #2896267)
• Lightning now supports bringing in front-end JavaScript libraries with Composer, via Asset Packagist. To take advantage of this in your Composer-based Lightning project, follow the instructions at http://lightning.acquia.com/blog/round-your-front-end-javascript-libraries-composer (GitHub #431)
• Lightning Core no longer has a hard dependency on the Metatag or Menu UI modules. (GitHub #418, #420 and #427)
• Lightning no longer has an implicit hard dependency on the Bartik or Seven themes. (Issue #2899017)
• Page Manager is no longer required by Lightning Layout. It is still shipped with Lightning, but is not a dependency and will be removed from Lightning in the next release. If you are using Page Manager, you must explicity include it as a dependency of your project. Otherwise, you should uninstall it as soon as possible. (GitHub #410)
• Quick Edit is no longer visible on published content when Lightning Workflow is enabled, because Quick Edit does not deal properly with forward revisions. In Lightning, you will only be able to use Quick Edit on unpublished drafts. (Issue #2894874)
• Split scheduled update functionality into a sub-component of Lightning Workflow, installed by default on new Lightning sites. (Issue #2893542)
• Panels was updated to version 4.2. (GitHub #409)
• Removed unnecessary lightning_core_entity_load(). (GitHub #406)