'Artifact update problem' when PHP project is in subfolder

[ThibaultVlacich]

What Renovate type are you using?

Hosted App on GitHub.

Describe the bug

On my repository, I have a PHP project in a subfolder. The composer.json file is in that subfolder. When I get a PR to update a dependency, I'm getting this error message:

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻️ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you check the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: server/composer.lock

Command failed: docker run --rm -v "/mnt/renovate/gh/ThibaultVlacich/[redacted]":"/mnt/renovate/gh/ThibaultVlacich/[redacted]" -v "/tmp/renovate-cache":"/tmp/renovate-cache" -e COMPOSER_CACHE_DIR -w "/mnt/renovate/gh/ThibaultVlacich/[redacted]" renovate/composer bash -l -c "composer update sentry/sentry-symfony --with-dependencies --ignore-platform-reqs --no-ansi --no-interaction --no-scripts --no-autoloader"
Composer could not find a composer.json file in /mnt/renovate/gh/ThibaultVlacich/[redacted]
To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ "Getting Started" section

As you can see, it's trying to find the composer.json file in the root directory of the repository, and unsurprisingly it's failing...

The issue started less than a week ago, it was working fine before.

[rarkins]

Thanks for reporting. I found a bug where we weren't passing the current working directory to composer and it defaults to the root of the repo. The fix should go live within the app today and you can tick the rebase/retry box to regenerated correct PRs with composer.lock.

[renovate-release]

🎉 This issue has been resolved in version 19.115.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀