Skip to content

deps: upgrade gpui-component to upstream main (be3c841) and gpui to zed 1a246efd #174

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stippi merged 1 commit into from
Jul 30, 2026
Merged

deps: upgrade gpui-component to upstream main (be3c841) and gpui to zed 1a246efd #174

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,10 +171,11 @@ jobs:
sed -i.bak "s/^version = \"$CURRENT\"/version = \"$RELEASE\"/" "$crate_toml" && rm -f "$crate_toml.bak"
done
# Refresh only the workspace crate versions in Cargo.lock. A bare
# `cargo update` would re-resolve the unpinned git dependencies
# (gpui / gpui-component) and pull a second, incompatible copy of gpui
# into the graph. --workspace keeps those git deps at their locked
# commit so the subsequent `--locked` build stays reproducible.
# `cargo update` would re-resolve *all* dependencies; `--workspace`
# touches only our own crates. The gpui / gpui-component git deps are
# pinned to explicit revs in the root Cargo.toml `[patch]` section, so
# they stay at their locked commit either way and the subsequent
# `--locked` build stays reproducible.
cargo update --workspace
grep -m1 "^version = " crates/code_assistant/Cargo.toml

Expand Down
Loading
Loading