Chris DI'm considering renaming my PHP failed test runner Composer package to better represent that it works with both PHPUnit and Pest.
Any recommendations on the best way to do it? 🤷♂️
Tobias van Beek@chrisd create a new package that replace the current package and abandoned the old package while pointing to the new one.
The old one will keep working but people will see that it is abandoned with a replacement.
Optionally you could define that the new package replace the old one. (See https://getcomposer.org/doc/04-schema.md#replace ) but that could be more difficult to manage.
The old one will keep working but people will see that it is abandoned with a replacement.
Optionally you could define that the new package replace the old one. (See https://getcomposer.org/doc/04-schema.md#replace ) but that could be more difficult to manage.
@tvbeek that’s sort of what I was thinking, as I have seen other packages do the same. Is it typical to retain all of the versions from the old package in the new package?
@chrisd I think I should only keep the versions from the latest major version.