why not pushing for the beta only instead of allowing ^0.1 as well?

do we really would like to use library in the beta/alpha version stage? @theofidry @maks-rafalko

do we really would like to use library in the beta/alpha version stage?

Well, although we are safe since we are using composer.lock file, I would still avoid using beta versions as a direct dependencies in Infection.

As I understand, @snapshotpl wants to be able to install Infection to his project, where 1.0.0.@beta is already used.

What if I suggest you using Infection PHAR distribution instead and forget about conflicted dependencies ;) ?

@maks-rafalko that's great idea, however it's not simple to install and maintain infection's phar like phpstan or rector

I can download phpstan as phar via composer

I would still avoid using beta versions as a direct dependencies in Infection.

In this specific case we use the dev version (0.1) which is not any safer than a beta

What is the benefit to use PHAR through composer rather than just download it or use https://phar.io/ to manage PHARs?

I don't need to change nothing in my project. Like phpstan did in 0.12. After composer install I just get phar. In your case in need to change my local and production deployment process.

@snapshotpl any chance to update the PR? Would love to get this one merged :)

@theofidry thecodingmachine/safe is now in stable version :)

Thank you @snapshotpl