You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a focused branch-tip compatibility canary for the core Zed dependency graph, limited to Rust, TypeScript, and Dart.
The audited core graph is:
zed-cli -> zed-clients
zed-cli -> zed-interfaces
zed-cli -> zed-lock
zed-clients -> zed-interfaces
Existing zed-cli CI currently checks out zed-interfaces at 60a8ab55f8a55eb212a72dcb334c1c118047c7ef. The current zed-interfaces/main tip is 958d833fd6561492924aaa4ab71d14affdfad39d, which is 30 commits ahead, so normal green CLI CI does not prove current-tip compatibility.
What this adds
The canary resolves the current main tips for zed-interfaces, zed-clients, and zed-lock once, records their immutable SHAs, then validates exactly those revisions:
zed-interfaces: Rust, TypeScript, Dart
zed-clients: Rust, TypeScript, Dart, against the same exact zed-interfaces tip
zed-lock: Rust
zed-cli: Rust against the exact current zed-interfaces tip
No other language runtimes are exercised by this canary.
Actions remain commit-pinned and the workflow has read-only repository permissions.
Baseline evidence
The current exact-head CI for zed-clients is green and its main workflow already compiles/tests Rust, TypeScript, and Dart. Current zed-interfaces and zed-lock main CI are also green. This PR specifically closes the remaining branch-tip validation gap in the CLI dependency tree.
Validation for the new cross-tip canary is provided by this PR's own Actions checks.
The original canary correctly resolved current dependency tips, but its zed-cli lane was still compiling the PR branch itself. That branch had diverged from current main, so it was no longer sufficient evidence for current-tip CLI compatibility.
Commit 9a6acb5e62dc44b90702a5bb4eb3af895c6dad0f fixes that audit gap by resolving zed-cli/main in the same immutable snapshot as the dependency tips and compiling that exact CLI revision against the exact current zed-interfaces revision.
All intended jobs are green: zed-interfaces Rust/TypeScript/Dart, zed-clients Rust/TypeScript/Dart, zed-lock Rust, and current-main zed-cli Rust against the dependency tip. No other language runtimes are exercised by this canary.
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
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
Add a focused branch-tip compatibility canary for the core Zed dependency graph, limited to Rust, TypeScript, and Dart.
The audited core graph is:
zed-cli -> zed-clientszed-cli -> zed-interfaceszed-cli -> zed-lockzed-clients -> zed-interfacesExisting
zed-cliCI currently checks outzed-interfacesat60a8ab55f8a55eb212a72dcb334c1c118047c7ef. The currentzed-interfaces/maintip is958d833fd6561492924aaa4ab71d14affdfad39d, which is 30 commits ahead, so normal green CLI CI does not prove current-tip compatibility.What this adds
The canary resolves the current
maintips forzed-interfaces,zed-clients, andzed-lockonce, records their immutable SHAs, then validates exactly those revisions:zed-interfaces: Rust, TypeScript, Dartzed-clients: Rust, TypeScript, Dart, against the same exactzed-interfacestipzed-lock: Rustzed-cli: Rust against the exact currentzed-interfacestipNo other language runtimes are exercised by this canary.
Actions remain commit-pinned and the workflow has read-only repository permissions.
Baseline evidence
The current exact-head CI for
zed-clientsis green and its main workflow already compiles/tests Rust, TypeScript, and Dart. Currentzed-interfacesandzed-lockmain CI are also green. This PR specifically closes the remaining branch-tip validation gap in the CLI dependency tree.Validation for the new cross-tip canary is provided by this PR's own Actions checks.