Add source-fallback config option to disable/enable fallback on download failure
#12698
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
By default, Composer silently falls back to cloning from source when dist downloads fail. While convenient, this behavior can be problematic in production/CI environments where:
.gitdirectories and other VCS files, causing deployments to fail or behave unexpectedlyUsage
Config file:
{ "config": { "source-fallback": false } }Command line:
composer install --no-source-fallbackcomposer update --source-fallbackEnvironment variable:
COMPOSER_SOURCE_FALLBACK=0 composer installBehavior
When disabled and a download fails, Composer will display a clear error message explaining that fallback is disabled, rather than silently trying alternatives.
Changes
Fixes #4591