I'm publishing one of my packages (pipelines) via Github and Packagist gets the updates. My tags are vX.Y.Z --with the v prefix.

The main form of distribution is a phar file as it is a command-line utility.

Now I'm considering to do this similar as phpstan does, that is having one "channel" for the phar distribution via packagist due to dependencies/scoping/autoloading.

IMHO this makes really sense, but I'd like to not split my Git repository for that and just continue to do tagged releases via Git but as optimized Composer "packages".

Therefore I'm thinking about using a dev tag like devX.Y.Z which will then be used to build the Packagist release from as a simple git release with the real(tm) vX.Y.Z tag having the distribution objects only.

Now I know about but always had a bit of an understanding problem with the dev-* and *-dev rules and would benefit from some clarification which Git tags are picked up by Packagist.org/Composer and what the consequences of a devX.Y.Z or dev-X.Y.Z (mind the hyphen-minus) would be. E.g. "Bad Idea" situation. As the naming apart from the existing scheme is not yet set, I still have options.

It's also possible that I run some tests with a different repository but I'd thought I'd ask first in a discussion as others may have already experiences with this topic.