Hello! First of all, thanks for getting on board with Composer with us, and registering your module on Packagist! We rely on early adopters like you to push adoption, and are thrilled to see such an enthusiastic uptake of Composer :)
We've noticed that you're using the "silverstripe" vendor prefix, which should only be used for modules maintained by the SilverStripe Ltd. organization (details). We'd like to ask you to change your vendor prefix accordingly by changing the name key in your composer.json. Usually using your github name is a good idea. The fact that this repo is a SilverStripe module is already contained in the "type": "silverstripe-module" metadata.
In order to ensure existing links to the module continue to work, please add a "replace" key to your composer.json:
"replace": {"<old-name>": "*"}
If you have created branches and releases containing a composer.json file,
it is recommended that you push the change there as well (and create new releases).
Once the name change is committed, force update the module on Packagist.
Note that the name change is only for Composer, you can call your github repository
however you like.
Hello! First of all, thanks for getting on board with Composer with us, and registering your module on Packagist! We rely on early adopters like you to push adoption, and are thrilled to see such an enthusiastic uptake of Composer :)
We've noticed that you're using the "silverstripe" vendor prefix, which should only be used for modules maintained by the SilverStripe Ltd. organization (details). We'd like to ask you to change your vendor prefix accordingly by changing the
namekey in yourcomposer.json. Usually using your github name is a good idea. The fact that this repo is a SilverStripe module is already contained in the"type": "silverstripe-module"metadata.In order to ensure existing links to the module continue to work, please add a "replace" key to your composer.json:
"replace": {"<old-name>": "*"}If you have created branches and releases containing a composer.json file, it is recommended that you push the change there as well (and create new releases). Once the name change is committed, force update the module on Packagist.
Note that the name change is only for Composer, you can call your github repository however you like.
Thanks Ingo Schommer, SilverStripe Core Developer