Frage

I am trying to package a module for use with composer. I have a valid composer file and I am able to install it with composer, but only when I specify that it should use dev releases (via the "@dev" version directive or minimum stability dev). I am having trouble packaging my repo so that it is seen as a master release.

I found a composer document about aliases that seems to be made for my case, but I cant get it working. Heres the relevant portion of my composer.json:

    "extra": {
    "branch-alias": {
        "dev-master": "1.0"
    }
}

Also for reference heres the require from my main projects composer file:

"require": {
    "misterglass/kohana-twig"  : "1.*"
},

And the actual error from composer is:

Problem 1 - The requested package misterglass/kohana-twig 1.* could not be found.

War es hilfreich?

Lösung

According to some helpful people on the #composer IRC channel, aliases are just to associate different versions to each other, and not to assign stability.

In order to for composer to consider it stable, you need to add a tag, which you can do on the command line or by creating a release in github.

Lizenziert unter: CC-BY-SA mit Zuschreibung
Nicht verbunden mit StackOverflow
scroll top