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.Lightning 8.x-1.10 is a new feature release (see our VERSIONS.md for more information on tag nomenclature). Lightning 8.x-1.10 will also be the first version of Lightning that depends on Drupal core ^8.2.0.
We expect to make this release at the same time Drupal Core 8.2.x is released - currently scheduled for 6 OCT 2016.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | 2699121-10.patch | 709 bytes | webflo |
Comments
Comment #2
balsamaComment #3
balsamaComment #4
anruetherLightning 1.10 is linked on the project site, but composer doesn't update. Is that happening later, or is there anything particular to do?
Comment #5
phenaproxima@anreuter: In your composer.json, what version constraint do you have for drupal/lightning?
Comment #6
anruetherThe default one which is used when installing via the composer command from the project page I guess:
"drupal/lightning": "^8.1.0"Comment #7
Ralf Eisler CreditAttribution: Ralf Eisler commentedThe same here with constraints "drupal/lightning": "^8.1.0".
Sidenote: Installing a new project still loads:
- Installing drupal/lightning (8.1.06)
Comment #8
balsamaHmmm. Packagist clearly has the latest version:
https://packagist.drupal-composer.org/packages/drupal/lightning
The only thing I can think to tell you is to clear your composer cache ($ composer clear-cache). Other than that, you could specifically require 8.1.10 ("drupal/lightning": "8.1.1")
Comment #9
balsamaAha. Turns out it's multiversion depending on a bad version of entity_storage_migrate.
Composer can't resolve that bad/malformed version of entity_storage_migrate so it reverts back to v1.06 of lightning which didn't require multiversion.
We're going to push a commit that depends on the dev version of multiversion for the time being (which doesn't require entity_storage_migrate at all. Standby.
Comment #10
webflo CreditAttribution: webflo at UEBERBIT GmbH commentedpackagist.drupal-composer.org reads some information from the make files as well. I think the branch in the makefile is wrong and this leads to a broken version constraint later ...
Comment #12
balsamaSo the problem was actually in the way that drush make-convert was converting the dev requirement in composer.lock to the .make format - which packagist uses in addition to the composer.json file. Thanks to webflo for tracking this down.
Fix is committed to HEAD and a patch has been submitted to drush: https://github.com/drush-ops/drush/pull/2392
You'll have to pull head of lightning, or better, the commit that fixed this:
"drupal/lightning": "dev-8.x-1.x#942a15ed7212741b00036d2be9a15283762d7207"