Closed (fixed)
Project:
Lightning
Version:
8.x-4.000
Component:
Documentation
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Jun 2019 at 18:19 UTC
Updated:
2 Jul 2019 at 19:59 UTC
Jump to comment: Most recent
Comments
Comment #2
dmlb2000 commentedSome repository references...
The install profile https://github.com/pacifica/pacifica-userinterface-core
The project template https://github.com/pacifica/pacifica-userinterface-project
Comment #3
phenaproximaThis was due a backwards compatibility break in the latest release of the OpenAPI module. I have rolled a new release of Lightning API (8.x-4.2), so if you update your Lightning now (just a simple
composer updateshould do it), you shouldn't have a problem.Comment #4
dmlb2000 commentedOkay, so this doesn't work because the lightning install profile doesn't have the right version now.
Is there a pull request I need to comment on to get the lightning profile updated to 8.x-4.2?
Comment #5
dmlb2000 commentedI couldn't find one so I put one in myself. https://github.com/acquia/lightning/pull/654
Comment #6
phenaproxima@dmlb2000, you should be able to update to the latest version already. Lightning does not pin the version number of lightning_api, so you should be able to get 4.2 with
composer update. However, I do see your pull request and I will merge it if it passes Travis CI, since it's definitely a good idea to make this change now and prevent future Lightning users from getting the 8.x-4.1 version.