Repository navigation
ci: require CLI Composer trust verification - #242
Merged
Merged
Conversation
|
rmcdaniel
marked this pull request as ready for review
October 23, 2026 05:39
This was referenced Oct 23, 2026
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.
Continues #237 after durable-workflow/cli#63 delivered the effective Composer
trust guards. CLI source merges as
535cb6e9b949aadf53c8b0313963577cccfec43c,exact qualified tree
4e377a3eefa6e13a0ec91d495ecd222515904569.Independent main Build 39906101401 passes all PHP, PHAR, reproducibility and
target-qualification checks. Sonar and the actual default-setup language
analyses were reviewed on the candidate; the summary warning remains recorded
in that PR.
This adds only
cli.composer_trust_required: true. It prevents a future changefrom dropping every guard and thereby leaving no automatic opt-in to Composer
sink validation. The stricter temporary policy already refused the preceding
CLI workflows and accepted the delivered source. Normal shared-policy checks
must qualify this exact flag change.
No validator, threshold, protected-main workflow, App exception, credential,
runtime or product version changes. Protected native publisher acceptance and
the other #237 obligations remain separate.