Can you please follow those recommendation for further updates:
Create a tag (https://git-scm.com/book/en/v2/Git-Basics-Tagging#_annotated_tags) every time you make a release (i.e merging PR/substantial commit to master...). By doing this, this allow users to have a stable version of your code (easier to reproduce bug and identify responsible revision of your code)
Add packagist webhook to your github settings (https://packagist.org/about#how-to-update-packages). This would update packagist to distribute your codebase with all your tags. With this action, each time you release a stable tag or merging something to master, users could be able their dependencies using composer
Remove version number from composer.json. This is not required for releasing (will work with the use of git tags) and will ease maintaining.
For example, your actual master fixes most of the issues. But this version is neither a stable tag nor published to packagist (dev-master is an old release) so no one is able to download your codebase via composer. One has to git clone directly in his codebase to be able to use your latest fixes.
Those recommendations could reduce false positive issues, and thus, giving a clearer view for users and contributors (you included), or ease use as dependency (easy update with composer)
Hey Kyran, Thank you very much for your work.
Can you please follow those recommendation for further updates:
composercomposer.json. This is not required for releasing (will work with the use of git tags) and will ease maintaining.For example, your actual master fixes most of the issues. But this version is neither a stable tag nor published to packagist (
dev-masteris an old release) so no one is able to download your codebase viacomposer. One has to git clone directly in his codebase to be able to use your latest fixes. Those recommendations could reduce false positive issues, and thus, giving a clearer view for users and contributors (you included), or ease use as dependency (easy update with composer)