chore(gpui): bump the git gpui stack · zed 86effffd→a12ed0fb, gpui-component dadfca9→6ef264a4#226
Merged
Merged
Conversation
…mponent dadfca9→6ef264a4 First successful bump since the June two-copies desync: gpui-component's 2026-06-15 'Lock GPUI version' commit pinned zed at a rev while our gpui dep floats on HEAD, which Cargo treats as two different sources (two gpui copies in the lock). Upstream removed the pin on 2026-07-06; this bump resolves to a single gpui copy again. deny.toml re-evaluation per its own header: - drop the RUSTSEC-2025-0052 (async-std) ignore — async-std left the tree - prune zed-industries/wgpu from allow-git — no longer a lock source - repoint the two font-stack ignores (0192/0206) at tracking issue #224 Evidence: - cargo fmt --all --check clean - just check green (clippy -D warnings, default + tray) - TMPDIR=/tmp cargo test --workspace: 450 passed, 2 ignored (39 suites) - cargo deny check: advisories ok, bans ok, licenses ok, sources ok - app smoke test: QA vault unlock → Portfolio renders correctly (shots on PR)
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.
What
First
just bump-gpuisince the June desync — moves the pinned git gpui stack five weeks forward:86effffd(2026-06-05)a12ed0fb(2026-07-13)dadfca9(2026-06-05)6ef264a4(2026-07-13)Diff is
Cargo.lock+deny.tomlonly — no code changes were needed; the workspace compiles clean against zed HEAD.Why it works again
gpui-component's 2026-06-15 "Lock GPUI version for pass build" commit pinned zed at an exact rev while our
gpui = { git = zed }floats on HEAD. Cargo treats bare-git and git+rev as different sources, so a bump put two gpui copies (two zed revs) in the lock and nothing type-checked across the boundary. Upstream removed the pin on 2026-07-06 (f0abdd9f); this lock resolves to a single gpui copy again. Toolchain unchanged (zed still requires 1.95.0).deny.toml re-evaluation (per its own "re-evaluate on each bump" header)
zed-industries/wgpufromallow-git— no longer a source in the lock.Evidence (DoD)
Visual verification (QA vault, live app on the bumped stack)
Unlock screen and post-unlock Portfolio both render correctly — fonts, amber trust cues, meta rail, fork banner, mono numerals all per
DESIGN.md: