Skip to content

Bump gpui-pre to 0.3.7 - #21

Merged
madcodelife merged 1 commit into
mainfrom
bump-gpui-pre-0.3.7
Sep 29, 2026
Merged

madcodelife merged 1 commit into
mainfrom
bump-gpui-pre-0.3.7

Conversation

@madcodelife

@madcodelife madcodelife commented Sep 29, 2026 •

Copy link
Copy Markdown
Member

What

  • Bump the pinned gpui-pre / gpui-pre-wgpu / gpui-pre-reqwest-client deps (lib + example) from =0.3.6 to =0.3.7.
  • Adapt the iOS and Android windows to gpui-pre-wgpu 0.3.7. WgpuRenderer::gpu_specs now returns Option<GpuSpecs>, so gpu_specs() flattens it with and_then instead of wrapping it in a second Option.
  • Move the example's gpui-kit rev from 13c716b (0.6.5, on gpui-pre 0.3.6) to 2ec5696 (0.7.0, on gpui-pre 0.3.7).

Why

gpui-kit 0.7 requires gpui-pre =0.3.7, but gpui-mobile pins =0.3.6. The two exact pins can't be reconciled, so no app can depend on gpui-kit 0.7 and gpui-mobile at the same time.

Verified

  • cargo check --lib --target aarch64-apple-ios-sim
  • cargo check --lib --target aarch64-linux-android
  • cargo check --manifest-path example/Cargo.toml --target aarch64-apple-ios-sim
  • cargo check --all-targets, cargo test --lib (46 passed) and cargo fmt --all -- --check on the host

gpui-pre-wgpu 0.3.7 returns `Option<GpuSpecs>` from
`WgpuRenderer::gpu_specs`, so the iOS and Android windows flatten it
with `and_then` instead of wrapping it again. The example moves to the
gpui-kit revision built on gpui-pre 0.3.7.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@madcodelife
madcodelife merged commit 9075e3a into main Sep 29, 2026
@madcodelife
madcodelife deleted the bump-gpui-pre-0.3.7 branch September 29, 2026 05:54
@madcodelife madcodelife mentioned this pull request Oct 9, 2026
madcodelife pushed a commit that referenced this pull request Oct 9, 2026
Two commits:

### 1. Bump gpui-pre to 0.3.8
Bumps the `gpui-pre` family (`gpui-pre`, `gpui-pre-wgpu`) from `=0.3.7`
to `=0.3.8`, following the previous bumps (#18 → 0.3.6, #21 → 0.3.7).

**Why:** `gpui-kit` has advanced to `0.7.1`, which requires `gpui-pre
0.3.8`. Downstream consumers that pull **both** `gpui-mobile` and
`gpui-kit` (e.g. ai-chat's `examples/ios` iOS static lib) currently
can't resolve a consistent set: `gpui-kit 0.7.1` wants `gpui-pre 0.3.8`
while `gpui-mobile` pins `=0.3.7`, so the iOS build fails (`cannot find
RoundedFrameCover in gpui_kit::base`, an API that only exists on the
0.7.1 line).

### 2. Pin libc to 0.2.189
`libc 0.2.190` dropped the iOS `_dyld_*` symbol declarations that
`backtrace`'s `symbolize/gimli/libs_macos.rs` relies on, so a fresh
dependency resolution breaks `cargo check --target
aarch64-apple-ios[-sim]` (`E0425: cannot find _dyld_image_header in
libc`). This already reddened `main` (#26) independently of this bump;
pinning to the last good release keeps the apple-ios CI green until a
fixed libc (>0.2.190) ships.

### Verification
- `gpui-pre` / `gpui-pre-wgpu` / `gpui-pre-reqwest-client` `0.3.8` are
published on crates.io.
- Local `cargo check` for `aarch64-apple-ios` and
`aarch64-apple-ios-sim` both finish clean with this branch.
- With this branch patched in, ai-chat's `examples/ios` resolves
`gpui-kit 0.7.1` + `gpui-pre 0.3.8` + `libc 0.2.189` and `cargo check
--target aarch64-apple-ios-sim` finishes with no errors.

---------

Co-authored-by: yuanzhuang-svg <273899003+yuanzhuang-svg@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant