search

yireo / Yireo_NextGenImages

44 stars 26 forks source link

Unable to install the latest version of this module via Composer #26

Closed vigneshvelaam closed 2 years ago

vigneshvelaam commented 2 years ago

We are unable to install the latest version of this module via Composer

We are using Hyva them in our Magento. Hyva compatible here: https://gitlab.hyva.io/hyva-public/module-tracker/-/issues/11 https://gitlab.hyva.io/hyva-public/module-tracker/-/issues/6

But while we installing the Hyva compatible module using composer, yireo base modules are installing again with old version. Installing dependencies from lock file (including require-dev) Package operations: 3 installs, 0 updates, 0 removals

-- yireo/magento2-webp2 --> OK installed latest version yireo/magento2-next-gen-images --> NOT OK installed OLD version: 0.2.13

We need to update the Yireo NextGenImages module to latest version using composer only. From 0.2.13 To 0.3.0

We are getting the following error when trying to update: [InvalidArgumentException] Could not find package yireo/magento2-next-gen-images in a version matching 0.3.0

Kindly check it and let us know.

Thank you!

jissereitsma commented 2 years ago

Thanks for opening a ticket. You mention NextGenImages version 0.3.0 as a requirement. But that version is actually not released yet: https://github.com/yireo/Yireo_NextGenImages/releases It is mentioned in the development version of composer.json of WebP2. But that composer file is not included in any release. The latest release of WebP includes a requirement for NextGenImages 0.2.X: https://github.com/yireo/Yireo_Webp2/blob/0.11.4/composer.json#L22

Could you find out why NextGenImages 0.3.0 is needed, and not version 0.2.X? Running a test installation for this does not lead to the same situation in my case.

jissereitsma commented 2 years ago

I guess this was related to the fact that on GitHub the composer files were updated but not yet released? The current releases have been made. Feel free to re-open this ticket if this same issue is popping up. If another issue pops up, due to the release, feel free to open a new ticket.