Using versions and tagging
It is fully expected that your package will not be perfect the moment you publish. Even if you did somehow manage to achieve perfection, the world keeps changing, and you might find that the latest PHP version that has just come out requires some tweaks to your code. You need to provide a mechanism for projects that are using your package to make sure they only get the known, safe versions that they want.
When you update your library and hit a stable point that you would like to release as a new version that is ready to be used in production projects, all you need to do is create a Git tag with a semantic version (to be explained soon) and push this up to the VCS that Packagist is connected to – for example, GitHub:
Resources to learn Git
https://try.github.io/
Creating a Git tag
Before you can create a tag, you must have created at least one commit. In general, there will be a whole sequence of commits leading up to the point where...
