You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It turns out that ArrayLoader doesn't populate the repositories section of the Package objects it creates, so the code that attempts to merge repositories with the base package doesn't fire even if the package declares custom repositories. Likely related to https://getcomposer.org/doc/faqs/why-can%27t-composer-load-repositories-recursively.md
The text was updated successfully, but these errors were encountered:
Add initial support for the upcoming Composer 2.0 release:
* Allow either ^1.1 or ^2.0 composer-plugin-api
* Implement new PluginInterface methods (as no-op)
* Prefer InstallerEvents::PRE_OPERATIONS_EXEC over
InstallerEvents::PRE_DEPENDENCIES_SOLVING when available
Bug: T248908
Co-authored-by: Bryan Davis <bd808@wikimedia.org>
It turns out that ArrayLoader doesn't populate the repositories section of the Package objects it creates, so the code that attempts to merge repositories with the base package doesn't fire even if the package declares custom repositories. Likely related to https://getcomposer.org/doc/faqs/why-can%27t-composer-load-repositories-recursively.md
The text was updated successfully, but these errors were encountered: