Is it possible to mark future PHP versions as untested but available in Composer? #1204
Description
We restrict PHP version to the current latest.
But if we could in some way allow a later version under certain conditions, marked as 'use at your own risk', that would, I think, be helpful to both us and developers using our software.
Recently, support for the latest PHP version has simply involved a change to the maximum PHP version in composer.json. But we have to provide a new release to support it. And some folk have raised issues because we haven't yet done that, and they are unable to test aginst, say, the next PHP alpha.
My rationale here is ZCO (zero cost of owenership) - we shouldn't have to keep making new releases if there is no change in the software - it's a waste of everyone's time.