You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our case, there was a package with two branches which had another name in the composer.json and we were not able to install the package by the name provided in the composer.json on the develop branch.
composer.json on broken branch:
"name": "vendorFoo/barWrong",
composer.json on develop branch:
"name": "vendorFoo/barRight",
The resulting packages.json file showed only vendorFoo/barWrong, but not vendorFoo/barRight.
To Reproduce
Create a new project with a composer.json, using vendorfoo/bar as the name
Commit and push the code
Create a new branch and change the name of the package in the composer.json to vendorbaz/bar. I'm not sure how to force the new branch to be on top of the other available branches and tags (alphabetical order?)
Remove the cached json files on your server
Regenerate the packages.json file
Take a look into that file and check the name of the package, only one package should be available (either vendorfoo/bar or vendorbaz/bar)
Expected behavior
I expected to be able to install both packages.
The text was updated successfully, but these errors were encountered:
Describe the bug
The package name is always fetched from the first element in the
json
file as you can see here:gitlab-composer-repository/src/RegistryBuilder.php
Lines 266 to 273 in 0c1a99a
In our case, there was a package with two branches which had another
name
in thecomposer.json
and we were not able to install the package by the name provided in thecomposer.json
on thedevelop
branch.composer.json
on broken branch:composer.json
ondevelop
branch:The resulting
packages.json
file showed onlyvendorFoo/barWrong
, but notvendorFoo/barRight
.To Reproduce
vendorfoo/bar
as thename
name
of the package in thecomposer.json
tovendorbaz/bar
. I'm not sure how to force the new branch to be on top of the other available branches and tags (alphabetical order?)json
files on your serverpackages.json
filename
of the package, only one package should be available (eithervendorfoo/bar
orvendorbaz/bar
)Expected behavior
I expected to be able to install both packages.
The text was updated successfully, but these errors were encountered: