Builds failing with composer plugin error

[javabudd]

Bug Report

| Version(s) | 2.5.x

Summary

Builds against the 2.5.x branch (and possibly others) are failing due to a composer 2 security setting regarding allowable plugins. Example of a failed build that had no code changes and still failed. This could be happening on many Laminas libraries as it seems like it stems from laminas-ci-matrix-action.

Current behavior

All Github Actions builds are failing on the 2.5.x branch.

How to reproduce

Create a pull request into the 2.5.x branch to trigger a build.

Expected behavior

Builds should pass assuming no code changes have been made.

[Ocramius]

Seems to just be an issue with very old composer.json, while composer/composer:^2.3 onwards broke BC by introducing required config for any plugins to be run.

This section needs adjustment:

api-tools-doctrine/composer.json

Lines 20 to 22 in 675e8ee

	"config": {
	"sort-packages": true
	},

Here's an example of how plugins are configured in laminas/laminas-servicemanager:

https://github.com/laminas/laminas-servicemanager/blob/166c5687ac2f48790fed854387327da28afbf088/composer.json#L23-L33

[javabudd]

Good find, I'll submit a PR to fix.

[javabudd]

new PR that addresses the issue:

#35