Looks like I got this the wrong way around - if we have any data in the repositories.json file for a repo, we were adding installer for it (even if it shouldn't have installer)!
Now we're only adding installer for repos which need it - either because they explicitly need it, or because we can see from their composer package type that they're a Silverstripe CMS module
Looks like I got this the wrong way around - if we have any data in the repositories.json file for a repo, we were adding installer for it (even if it shouldn't have installer)!
Now we're only adding installer for repos which need it - either because they explicitly need it, or because we can see from their composer package type that they're a Silverstripe CMS module
Issue