Repository navigation
test: certify zed-cli #388 with GitHub-only outage recovery - #3
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.
Independent black-box certification for
zed-pkg/zed-cli#388, pinned to exact candidate SHA7032ceb8423ec97437d4103e7939a994606bc386.The workflow deliberately makes the Zed registry unreachable, disables GitHub credentials, points R2 at a dead loopback endpoint, and then proves Go/Python/Dart/Node/Gleam dependencies can be resolved and materialized directly from GitHub. It also requires byte-identical clean-store lock resolution, frozen replay from a third empty home, focused smart-HTTP parser/degradation tests, and fail-closed behavior when source fallback is disabled.
This test repository is independent promotion evidence; it does not relax the product repository's own outage gate.