Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Per https://www.drupal.org/node/2935137
Before:
$ composer validate
./composer.json is valid, but with a few warnings
See https://getcomposer.org/doc/04-schema.md for details on the schema
License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0+-only" or "GPL-2.0+-or-later" instead
require.drupal/lightning_api : exact version constraints (1.x-dev) should be avoided if the package follows semantic versioning
require.drupal/lightning_core : exact version constraints (1.x-dev) should be avoided if the package follows semantic versioning
require.drupal/lightning_layout : exact version constraints (1.x-dev) should be avoided if the package follows semantic versioning
require.drupal/lightning_media : exact version constraints (1.x-dev) should be avoided if the package follows semantic versioning
require.drupal/lightning_workflow : exact version constraints (1.x-dev) should be avoided if the package follows semantic versioning
After:
$ composer validate
./composer.json is valid, but with a few warnings
See https://getcomposer.org/doc/04-schema.md for details on the schema
require.drupal/lightning_api : exact version constraints (1.x-dev) should be avoided if the package follows semantic versioning
require.drupal/lightning_core : exact version constraints (1.x-dev) should be avoided if the package follows semantic versioning
require.drupal/lightning_layout : exact version constraints (1.x-dev) should be avoided if the package follows semantic versioning
require.drupal/lightning_media : exact version constraints (1.x-dev) should be avoided if the package follows semantic versioning
require.drupal/lightning_workflow : exact version constraints (1.x-dev) should be avoided if the package follows semantic versioning
Comment | File | Size | Author |
---|---|---|---|
update-gpl-license.patch | 401 bytes | anavarre |
Comments
Comment #2
phenaproximaI see no reason not to commit this, but I'd like to get @balsama's opinion.
Comment #4
balsamaCommitted. Thanks!