Early return skips lockedDatabase detection when isUpgrade is already set

If isUpgrade is already true (set explicitly in the saved config) but lockedDatabase is null, this early return means the database auto-detection never runs. The lockedDatabase will remain null even though the installation files are present and the database could be inferred.

If there is a scenario where isUpgrade can be persisted as true without a corresponding lockedDatabase value, the installer may behave incorrectly. Consider checking lockedDatabase independently:

private function autoDetectUpgrade(Config $config): void
{
    $basePath = $config->isLocal() ? '/usr/src/code' : (getcwd() ?: '.');
    $composePath = $basePath . '/docker-compose.yml';
    $envPath = $basePath . '/.env';

    if (!file_exists($composePath) && !file_exists($envPath)) {
        return;
    }

    if (!$config->isUpgrade()) {
        $config->setIsUpgrade(true);
    }

    if ($config->getLockedDatabase() !== null) {
        return;
    }

    $database = $this->detectDatabaseFromFiles($composePath, $envPath);
    if ($database !== null) {
        $config->setLockedDatabase($database);
    }
}

Redundant fallback regex loop

The second foreach loop (lines 241–245) is unreachable in practice. The first preg_match_all regex already includes the alternative (\w+): which will match any YAML key at the start of a line — including mariadb:, mongodb:, and postgresql:. In a valid docker-compose.yml, preg_match_all will almost always return a positive count (e.g. from version:, services:, etc.), enter the if block, and evaluate the same service names against $dbServices.

The second loop can only execute if preg_match_all returns false (a regex engine error) or 0 (no matches at all — essentially impossible in a non-empty compose file). Consider removing it to simplify the logic: