Open asispts opened 1 year ago
Just want to share with anyone else. You can use ENV to skip using build cache.
See: https://vercel.com/docs/concepts/deployments/troubleshoot-a-build#managing-build-cache
Hi @asispts. Do you have composer.lock versioned in your project?
Hi @asispts. Do you have composer.lock versioned in your project?
Yes
So let me summarize this problem.
/api/index.php
.composer update
or composer update <package name>
.Right?
Yes, that's the steps to reproduce the issue. However, on the step 3, it's better to add a new package and use it in /api/index.php
.
Bug report
Description
When modify
composer.json
(e.q: add/remove a package), build process always fail to detect the change. The build process always use the same cache.Composer validation shows that
composer.json
is valid.Solution
Redeploy without using existing build cache manually.