Tagging composer releases and version tags (git; vX.Y.Z / devX.Y.Z) #12357
-
|
I'm publishing one of my packages (pipelines) via Github and Packagist gets the updates. My tags are 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 Now I know about but always had a bit of an understanding problem with the 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. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
The devX.Y.Z tags will be ignored by packagist as they are invalid version numbers, so I think this works for your use case? |
Beta Was this translation helpful? Give feedback.
-
|
Hey, yes, I think so, I'll give a try. Thanks for the clarification @Seldaek And thinking, in regard to the valid version numbers: Is it possible to use four (numbered) segments in "v" prefixed tags as well? IIRC correctly, internally Composer used four parts. Or is the fourth position blocked for stability flags in tags (alpha, beta ...)? Example Tag: v4.3.2.1 |
Beta Was this translation helpful? Give feedback.
-
|
Yes that's correct you can do 1.2.3.4 |
Beta Was this translation helpful? Give feedback.
The devX.Y.Z tags will be ignored by packagist as they are invalid version numbers, so I think this works for your use case?