Repository navigation
Require Composer trust for Rust Avro consumers - #241
Merged
Merged
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.
Continues #237 after durable-workflow/sdk-rust#125.
Require the existing Composer network-trust guard for the Rust SDK target.
Its official Avro consumer installs PHP dependencies. Without this target
requirement, removing the last verifier action would also disable the automatic
scan. The requirement keeps that dependency request covered after future edits.
This changes one existing policy flag. It adds no workflow, token, App or
protected-main exception. Merge follows the Rust SDK caller's qualified merge.
The exact Rust caller passed current validation with this flag enabled locally.
Rust SDK #125 is merged at
2c2f3dc8, exact qualified tree2c0323c4,after all 17 applicable checks passed. This policy candidate
b06f66aepasses all seven checks, including shared contracts and Sonar. The issue API
has zero OPEN/CONFIRMED findings. Protected-main proposal #240 and its missing
account/review/live-pilot requirements remain separate and unactivated.
Normally merged at
1cedba6650fab7a0dc6b0c032b2e217536d507a0, with exactqualified whole tree
6612f647caf77d9aabb5c222b7598c0d1947f054.The remote branch is deleted and independently verified absent.