mburumaxwell
commented
2 months ago Looking at this, it seems the url is present where you would have instead set the host.
Maybe we need to add a host parameter when processing the registries of type composer-repository.
In the meantime, could you try adding the host parameter in your config file?
version: 2
registries:
composer:
type: composer-repository
url: 'https://repo.*****.nl'
host: 'repo.*****.nl' # <-- this here
username: '*****@*****.nl'
password: ${{REPO_API_KEY}}
updates:
- package-ecosystem: "composer"
directory: "/"
target-branch: "main"
registries:
- composer
schedule:
interval: "daily"Report back if this works so that we can bake it in.
Describe the bug I tried different options for providing a private composer-repository but the all seem to result in an error (See below). A while ago i had Dependabot running for the same repository but that stopped working one day and I only tried recently to get it working again. Previous it was working withthe following variable:
This stopped working one day and resulted in a 401 error form the custom repo. Since than I moved the configuration to a registry in the
dependabot.ymlfile:That doesn't result in a 401 anymore but it does raise the following error. I tried removing the schema from the repo url and a few other options but they all result in the same error.
Dependabot pipeline:
Dependabot.yml
Full output:
Please also note the difference between the generated
DEPENDABOT_EXTRA_CREDENTIALSand the one I previously used:Extension:
Installed version 1.31.0.826 (Latest) (Also tried with dockerImageTag 1.29 just to rule out the latest changes).