Closed joachimVT closed 2 years ago
Good catch, I thought about adding a section to the README.md file and then forgot about it. The main issue is that the package is available in both Packagist and Magento repo. And that is a problem (when version numbers are different), basically a new feature of Composer 2 to add a bit more security (e.g. you are not able to pull a hacked package from a 3rd party site).
You can fix it either the way you did it or declare the Magento repository as being non-canonical like this:
{
"repositories": [
{
"type": "composer",
"url": "https://repo.magento.com/",
"canonical": false
}
]
}
We are working on getting our module updated on Marketplace but the issue might occur in the future as we might not publish each minor version on Marketplace.
@joachimVT if you wanna help out, feel free to open a PR with some instructions on how to deal with the issue.
Hi @shochdoerfer
Thanks for the info, I'll open a PR.
Very much appreciated!
I'm trying to update the package to the new 5.0 release, but its working due to composer error.
Preconditions
Magento 2.4.3-p1
Force Login Module Version : 4.1.0 PHP version: 7.4
Steps to reproduce
Expected result
Actual result
Composer error:
Update
When I update the repositories section in composer.json it works
Any thoughts ?