Falha no deploy ao adicionar novos pacotes com Composer

[vvalentim]

Ambiente

Vercel CLI: 34.0.0
vercel-php: 0.5.5
Node.js (project settings): 18.x

Resumo

Falha ao tentar o deploy na Vercel quando é instalado um novo pacote com o Composer.

Logs

[17:15:23.261] Running build in Washington, D.C., USA (East) – iad1
[17:15:24.612] Retrieving list of deployment files...
[17:15:25.125] Downloading 78 deployment files...
[17:15:27.489] Restored build cache
[17:15:27.730] Running "vercel build"
[17:15:29.056] Vercel CLI 34.1.10
[17:15:31.060] 🐘 Downloading user files
[17:15:31.062] 🐘 Downloading PHP runtime files
[17:15:31.073] 🐘 Installing Composer dependencies [START]
[17:15:31.819] [5.2MiB/0.26s] Installing dependencies from lock file
[17:15:31.820] [5.2MiB/0.26s] Verifying lock file contents can be installed on current platform.
[17:15:31.831] [5.4MiB/0.26s] Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer update` or `composer update <package name>`.
[17:15:31.831] [5.4MiB/0.27s] - Required package "guzzlehttp/guzzle" is not present in the lock file.
[17:15:31.831] [5.4MiB/0.27s] This usually happens when composer files are incorrectly merged or the composer.json file is manually edited.
[17:15:31.831] [5.4MiB/0.27s] Read more about correctly resolving merge conflicts https://getcomposer.org/doc/articles/resolving-merge-conflicts.md
[17:15:31.831] [5.4MiB/0.27s] and prefer using the "require" command over editing the composer.json file directly https://getcomposer.org/doc/03-cli.md#require-r
[17:15:31.831] [5.3MiB/0.27s] Memory usage: 5.34MiB (peak: 5.92MiB), time: 0.27s
[17:15:31.849] Error: Exited with 4
[17:15:31.849]     at ChildProcess.<anonymous> (/vercel/path0/.vercel/builders/node_modules/vercel-php/dist/utils.js:182:24)
[17:15:31.849]     at ChildProcess.emit (node:events:518:28)
[17:15:31.850]     at ChildProcess.emit (node:domain:488:12)
[17:15:31.850]     at ChildProcess._handle.onexit (node:internal/child_process:294:12)
[17:15:31.917] Error: Command "vercel build" exited with 1
[17:15:32.032] Command "vercel build" exited with 1

[vvalentim]

Note

Utilizar a flag --force para ignorar o build cache nos deploys pelo CLI.

Aparentemente as alterações no composer.lock não estão sendo reconhecidas, o problema pode ser resolvido ao fazer deploy ignorando o build cache.

Referência para resolução: vercel-community/php#518