silverstripe/silverstripe-postgresql effectively defines its own matrix which includes hardcoded php versions.
This is because it obviously shouldn't be tested with mysql database.
We might need a new input to disable certain databases to handle this dynamically and avoid the postgres (and possible other db modules in the future e.g. aws) getting out of date.
silverstripe/silverstripe-postgresql effectively defines its own matrix which includes hardcoded php versions.
This is because it obviously shouldn't be tested with mysql database.
We might need a new input to disable certain databases to handle this dynamically and avoid the postgres (and possible other db modules in the future e.g. aws) getting out of date.