Request: Please Tag New Release v2.0.1 (Contains PHP 8 Composer Fix)

[josueisaacelias]

Hello,

I noticed that the latest stable tag, 2.0 (dated 2020-08-15), has a strict PHP constraint of ^5.5 || ^7.0 which prevents installation on PHP 8 environments (Composer Platform Check).

However, I see that the dev-master branch already contains the necessary correction (^5.5 || ^7.0 || ^8.0) as per the commit history (dated 2024-04-09).

Could you please create and push a new patch release tag (e.g., v2.0.1) containing this fix? This would allow users on PHP 8 to install a stable version without needing to rely on the unstable dev-master branch.

Thank you for your quick consideration.

[marm123]

Thank you for the report @josueisaacelias! @Alaa-abdulridha @ilyazub would it be possible to implement a quick fix so that the composer installs our dev-master branch by default instead of 2.0, as the former includes support for PHP 8.0?

[josueisaacelias]

@marm123
In my opinion, setting the dev-master branch as the default is not the standard or correct approach in Composer.

1. Composer Stability: Composer is configured by default to prefer stable tags (like 1.2.0 or 2.0) over any development branch (dev-master).
   

2. Current Behavior: When a user explicitly requests the ^2.0 range, the installation fails entirely. This is because the PHP constraint of the stable version 2.0 (^5.5 || ^7.0) is not satisfied by PHP 8.3.6, forcing Composer to abandon the operation and showing the 'installation failed' message, as clearly demonstrated in.
   

3. Current Workaround: Forcing the Unstable dev-master Branch to bypass the Composer constraint error on PHP 8 and access the corrected code, users are currently forced to require the unstable dev-master branch explicitly. As shown in, this command successfully installs the package, proving that the compatibility fix is complete:
   

The only way that i see to ensure all users on PHP 8 get the corrected code by default is to tag and push a new patch release, such as v2.0.1.

Once v2.0.1 is published, Composer will automatically select it, resolving the incompatibility for everyone without requiring users to set minimum-stability: dev.

Thank you

[marm123]

Thanks @josueisaacelias! You're probably right. Thank you so much for the feedback.

I'll leave the technical implementation to our engineers.