Uh oh!
There was an error while loading. Please reload this page.
chore: integrate hardened zed-lock v0.1.1 package - #205
Merged
Conversation
Update the zed-lock v0.1.1 integration branch with terminal-green current main, preserving the reviewed external package identity while incorporating Nix fixed-output and frozen-rendezvous canary repairs.
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Aug 5, 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 freeto 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.
Summary
zed-lockv0.1.1 package at immutable commita0dc78d385bc3ab553d3027b427f5f1428239c9c;zed-pkg/zed-lock@^0.1.1Zed package edge;crates/zed-locksource;Exact current-main composition
Current review head:
The branch is based on current
maincommit20567e717447c85c286cdf43dfefa2db83d2883c, including the terminal-green Nix fixed-output operation-lock repair and the frozen-rendezvous canary correction. The package integration no longer depends on a known failing repository-wide test.Published release evidence
The immutable
v0.1.1release targets exactlya0dc78d385bc3ab553d3027b427f5f1428239c9cand contains:zed-lock-0.1.1.crate— release asset digestsha256:ccb609710619dac7e80620a63b8f006c039602d36e543482e48c62a46205a6ac;zed-lock-0.1.1.crate.sha256— release asset digestsha256:5432f2312977033df6282ac57070b70c1b29f269903d273280e54210bb287771.The fully green Linux/macOS/Windows review matrix also retains Actions artifact
8942659707, namedzed-lock-0.1.1-42332da9abbf9638ea3a1f34eb225cf90900bbac, with ZIP digestsha256:1bb3235b54975054502823d734ed90fa2e0b78ead1f1a53c92829d4fc1db28ce.No existing release tag was overwritten and no crates.io publication is claimed.
Resolver-owned lock update
A branch-scoped workflow ran
cargo update -p zed-lock, asserted the exact v0.1.1 Git source, compiled all targets with--locked, committed only Cargo's generated lock delta, and removed itself. The review branch contains no write-enabled materializer workflow.Merge criteria
The exact-head repository matrix must be terminal-successful, including:
Superseded PR salvage
Supersedes: yes
.zpkg.toml, package-graph validation, and package dependency documentation in this PR