Pass --no-security-blocking only to composer install - #283
Open
sirreal wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
--no-security-blockingis an install/update option, but the genericcomposerpassthrough script passes it to every command, so anything else fails — e.g.npm run composer -- validate. The flag stays oncomposer:setup(install), and the passthrough keeps only--no-interaction.Verified in the PHP 7.4 wordpress container:
composer --no-interaction --no-security-blocking validateexits 1; without the flag it reports./composer.json is valid.composer install --no-interaction --no-security-blockingcontinues to work (unchangedcomposer:setuppath).Overlaps trivially with #276, which rewrites the same lines to derive the plugin directory; whichever lands second rebases in seconds.
🤖 Generated with Claude Code