you're right... can we change composer requirements to supporto only newer versions? Do I have to submit another PR?

@davedevelopment, should we raise the minimum supported PHP version of the library (e.g., to PHP 7.2) to allow changes like the one proposed in this PR to work on PHP 8.4?

• 1 already waiting for this. 👍

Any update on when this could be merged? Updated?

Any update on when this could be merged? Updated?

@PNardma , no updates.

@davedevelopment , ping.

Still no update. 😢

Still no update. 😢

@PNardman , Please try contacting@davedevelopment and other library maintainers by other communication channels (e.g. e-mail, twitter, etc.).

I'm sorry, I've been away from Hamcrest for some time and completely forgot about my responsibilities here. Generally, I'd say yes, 7.2 is very old and they can always version pin.

@davedevelopment , then here are the next steps:

1. create another PR that will set a minimum compatible PHP version to PHP 7.2 (or even PHP 7.4)
2. make a release
3. rebase & merge this PR

.

Opened#87

I've seen the 2.1.0 release which remove older php constraints, but - while it's merged to master - it doesn't include the implicit nullable fix, is there anything else we need to do?

Generally I'd avoid tagging for every fix, but go on then...