2

Magento sends an email to vendors before announcing officially about security patch to provide vendors possibility to upgrade/patch M2 beforehand.

We have two Commerce Edition projects with different credentials in auth.json:

{
    "http-basic": {
        "repo.magento.com": {
            "username": "*****************",
            "password": "*****************"
        }
    }
}

The interesting point, that for one project, new patched M2 is available, for another - not.

The result of:

composer show magento/product-enterprise-edition --all

will provide different results. Changed to the good keys for testing purpose, and it works (shows all available new versions)

Have someone faced with a similar issue?

Improve this question
2
  • updating the auth.json composer require magento/product-enterprise-edition 2.3.3 --no-update composer update working for me
    – sandip
    Sep 25, 2019 at 13:57
  • @sandip auth.json contains unique keys generated and provided specifically for each project, I can not use keys from another project. so did not get your point
    – sergio
    Sep 25, 2019 at 14:17

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Browse other questions tagged or ask your own question.