Noel Light-Hilary

I'm a bit short on time to look at the specifics of this one, but usually when we've seen this before it's an issue with the Subversion repository data/tags the...

This sounds like it would be good! There is a comment about WP core handling on #91 (see also https://github.com/outlandishideas/wpackagist/discussions/262) but it sounds like handling languages through Wpackagist ought to...

Hey @DesignyourCode, I'm not really sure what to do about this or what Wpackagist could be doing wrong. Do you have a bit more background about how the process works,...

Hey @DesignyourCode – while addressing some more pressing security updates late last year, I upgraded Wpackagist to use Composer v2 internally. This promptly broke the service for all devs on...

@strarsis I'm not sure this should be the default, especially as one previous request was basically the opposite: full text index / less exact matching on package titles. I guess...

Let's re-test this once recent refactor changes are out. See #350, #368

I think this is a live issue, but as you suggest is down to the published package data not being self-consistent in this particular case. I'm not sure the complexity...

> 👍 > > There's only one "major" issue with just changing the installer-paths (by workaround, or when adding a custom type), which is that mu-plugins won't be loaded from...

There have been a few releases since this, so I hope it will have resolved itself. Please reopen if not.

I think this was left open in error, _but_ #469 seems not to fix the problem successfully as we have new, similarly rare errors now because `EntityManagerClosed` is occasionally thrown...