-
Notifications
You must be signed in to change notification settings - Fork 16
DMore/chrome-mink-extension is breaking #21
Comments
This is due to acquia/blt-behat having locked its dependency to the Git repo rather than consuming a released package of DMore/behat-chrome-extension. Recently in https://gitlab.com/behat-chrome/chrome-mink-driver/-/issues/121 we made a relocation of the project on Gitlab (https://gitlab.com/dmore => https://gitlab.com/behat-chrome), but the Packagist component continues to have the same name ( Reproduction using a clone of this repo in Docker container (sandboxing from my available creds):
What wasn't anticipated with this was that Gitlab rejects access to the downloads rather than providing a redirect. Updated releases (which obtain working URLs) have been made, and can be used via an update. |
Hmm. Maybe I'm reading that wrong, after a moment the output continued:
My understanding was that Packagist serves the releases, not Gitlab. If I'm wrong, then it might be that a release needs to be made that Packagist can refer people to. |
If the thing breaking for you is the interactive prompt, try adding Composer will try the .zip URL which fails (sorry!), then fall back to source download and can continue. |
Released updated versions for your use:
Please update accordingly, but do not change your require from dmore/* to behat-chrome/* as that change has not been made upstream (and the behat-chrome/* packages referenced in #22 are unsupported placeholders only). |
The
dmore/behat-chrome-extension
repo looks to have been made private and requires a gitlab login. It looks like this repo has actually moved tobehat-chrome/behat-chrome-extension
. (v1.3.0 is the same commit)It should also be noted that
dmore/chrome-mink-driver
has also moved, but that is still a dependency ofbehat-chrome/behat-chrome-extension
. So maybe more breakage is to come?The text was updated successfully, but these errors were encountered: