Clarify passive readiness and XY-1304 integrity authority#1127
Merged
Conversation
…rity and causal no-mutation gate","authority":"manual","impact":"compatible"}
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
1 participant
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.
Summary
Validation
DEVELOPER_DIR=/Applications/Xcode-beta.app/Contents/Developer RUSTC_WRAPPER= cargo make checkcargo make test-vnext-architecturegit diff --check main...HEADNO_BLOCKING_FINDINGSfor fingerprintf91708c87255f7612864a23b1d125c876c3885238045ae5cb0dcda6a39577288Tracking
Related to XY-1336. This PR records current authority; it does not claim passive readiness is implemented or close the tracking issue.