Skip to content

chore(deps)(deps): bump egui-wgpu from 0.35.0 to 0.36.1 - #389

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/egui-wgpu-0.36.1
Closed

chore(deps)(deps): bump egui-wgpu from 0.35.0 to 0.36.1#389
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/egui-wgpu-0.36.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 17, 2026

Copy link
Copy Markdown
Contributor

Bumps egui-wgpu from 0.35.0 to 0.36.1.

Release notes

Sourced from egui-wgpu's releases.

0.36.1 - Sense::drag() bugfix

egui is an easy-to-use immediate mode GUI for Rust that runs on both web and native.

Try it now: https://www.egui.rs/

egui development is sponsored by Rerun, a startup building an SDK for visualizing streams of multimodal data.

0.36.0 - Improved mobile keyboard support

egui is an easy-to-use immediate mode GUI for Rust that runs on both web and native.

Try it now: https://www.egui.rs/

egui development is sponsored by Rerun, a startup building an SDK for visualizing streams of multimodal data.

Highlights ✨

Improved mobile keyboard support

Autocomplete, autocorrect and IMEs now work correctly on iOS and android (on eframe web)!

ScreenRecording_08-05-2026.11-48-49_1.MP4

Drag to reopen panels

You can now reopen closed panels by dragging the handle:

Screen.Recording.2026-08-05.at.11.45.10.mov

Window decoration theme is now synced with app theme

Previously, when switching themes, the window chrome (OS titlebar), stayed in the OS theme. Now, it syncs with the app theme:

Screen.Recording.2026-08-05.at.11.45.47.mov

... (truncated)

Changelog

Sourced from egui-wgpu's changelog.

0.36.1 - 2026-08-07

0.36.0 - 2026-08-05

Highlights ✨

This release drastically improves the mobile keyboard experience (when using eframe web). It also adds drag-to-open panels, window chrome theme sync and a lot of small bug fixes and improvements!

Improved mobile keyboard support

Autocomplete, autocorrect and IMEs now work correctly on iOS and android (on eframe web)!

ScreenRecording_08-05-2026.11-48-49_1.MP4

Drag to reopen panels

You can now reopen closed panels by dragging the handle:

Screen.Recording.2026-08-05.at.11.45.10.mov

Window decoration theme is now synced with app theme

Previously, when switching themes, the window chrome (OS titlebar) stayed in the OS theme. Now, it syncs with the app theme:

Screen.Recording.2026-08-05.at.11.45.47.mov

⭐ Added

🔧 Changed

🔥 Removed

... (truncated)

Commits
  • 4c1f2fa Release 0.36.1 - Fix Sense::drag bug
  • 42cd821 Fix Sense::drag detecting drags when clicking widget above it (#8396)
  • 2397194 Release 0.36.0 - Improved mobile keyboard support (#8390)
  • e37d44a Never run an egui pass when nothing will be shown (#8387)
  • 90e0302 Fix a few nightly clippy lints (#8388)
  • 5347b0a Fix window with a Grid being widenable but not shrinkable again (#8386)
  • 622bbbe Add drag-to-open for collapsible panels (#8363)
  • 98eab50 Treat a press that leaves a widget as a drag (#8365)
  • 78c0e39 Fix ScrollArea failure by handling horizontal and vertical scrolling separate...
  • 5c0b690 Add extra_text_line_spacing to control vertical spacing between text lines ...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [egui-wgpu](https://github.com/emilk/egui) from 0.35.0 to 0.36.1.
- [Release notes](https://github.com/emilk/egui/releases)
- [Changelog](https://github.com/emilk/egui/blob/main/CHANGELOG.md)
- [Commits](emilk/egui@0.35.0...0.36.1)

---
updated-dependencies:
- dependency-name: egui-wgpu
  dependency-version: 0.36.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from doublegate as a code owner August 17, 2026 10:10
@dependabot dependabot Bot added dependencies Dependency updates rust Rust / cargo dependencies labels Aug 17, 2026
@github-actions

Copy link
Copy Markdown

Antigravity review (Gemini via Ultra)

This PR updates the egui-wgpu dependency from 0.35.0 to 0.36.1.

Blocking issues

  • Correctness: egui-wgpu 0.36.1 depends on wgpu 30 and the egui 0.36 ecosystem, but Cargo.toml still specifies wgpu = "29" and egui = "0.35". This will lead to duplicated major versions in the dependency tree and cause compile-time type mismatch errors when sharing types like wgpu::Device or egui::Context between the app and egui-wgpu.

Suggestions

  • Cargo.toml, lines 138-140: Bump wgpu to version "30" and egui to "0.36" (along with any other related crates like egui-winit if used) in this same PR to keep the ecosystem versions unified.

Nitpicks

None found.

Automated first-pass review by agy on a self-hosted runner -- not a human review.

doublegate added a commit that referenced this pull request Aug 18, 2026
… wasm break) (#397)

* chore(deps): update the dependency graph; hold egui at 0.35 (upstream wasm break)

Consolidates the five open Dependabot PRs. Two are adopted, one is a CI
action pin, and three are declined on evidence rather than deferred.

ADOPTED. `cargo update` across the whole graph — roughly 80 crates, all
semver-compatible, no source changes required: `anyhow` 1.0.103 -> 1.0.104,
`cc` 1.4.0 -> 1.4.3, `cpal` 0.18.1 -> 0.18.2, the `futures-*` family
0.3.33 -> 0.3.34, the `icu_*` family 2.2 -> 2.3, `http` 1.4.2 -> 1.5.0,
`bstr`, `camino`, `clang-sys`, `darling`, `either` and the rest. Plus
`taiki-e/install-action` v2.85.10 -> v2.85.13 at both call sites in
`security.yml` (#387).

DECLINED, with the reason established by experiment: egui / egui-wgpu /
egui-winit 0.35 -> 0.36.1 (#389, #390, #391). `egui-winit` 0.36.1 does not
compile for `wasm32-unknown-unknown`, and RustyNES ships a wasm demo.

    error[E0407]: method `bytes` is not a member of trait `egui::DroppedFile`
      --> egui-winit-0.36.1/src/dropped_file.rs:19:5

The mechanism, since "blocked upstream" is not a diagnosis. egui 0.36 made
`DroppedFile` a trait and split it by target: `bytes_async` on wasm (files
can only be read asynchronously in a browser), `bytes` on native. Upstream
issue #8354, now closed, is the change that introduced it. `egui-winit`'s
`NativeFile` impl provides `path` + `bytes` with NO cfg gate, on a type
that holds a `PathBuf` and calls `std::fs::read` — inherently native. On
wasm it therefore implements a method the trait does not declare and omits
the one it does.

Nothing on our side can route around it. `mod dropped_file;` is
unconditional in egui-winit's `lib.rs` — not feature-gated, not
target-gated — so the module compiles on wasm whatever we do, and the fix
belongs upstream (a one-line cfg on the module and its `use`). No release
carries it: 0.36.1 is still the newest `egui-winit` on crates.io.

`wgpu` is held at 29 for the same reason: `egui-wgpu` 0.35 pins it, so 29
-> 30 cannot land ahead of the egui tier.

This confirms rather than assumes the note in `AGENTS.md` (added when the
migration was first attempted and parked on
`chore/egui-0.36-wgpu-30-blocked`). I re-ran the build instead of trusting
it, because a "blocked" note is exactly the kind of claim that silently
goes stale — and the useful output of re-checking is the specific method
name a future attempt needs, `bytes_async`, rather than a bare verdict.

Verified: workspace clippy, all four native feature combinations plus
`full`, BOTH wasm32 targets, rustdoc with warnings denied, the `no_std`
cross-build, 124 workspace test binaries, and `cargo deny check`
(advisories ok, bans ok, licenses ok, sources ok).

* docs(deps): record the egui 0.35 hold where the pin lives

Review suggestion, taken. The reason egui / egui-wgpu / egui-winit are held at
0.35 was in the commit body and the PR — neither of which anyone reads while
editing `Cargo.toml`, which is exactly where the next person (or the next
`cargo update --aggressive`) will decide to move them.

The comment carries the failing error verbatim, the mechanism (egui 0.36 split
`DroppedFile` by target — `bytes_async` on wasm, `bytes` on native — and
`egui-winit`'s `NativeFile` impl provides `path` + `bytes` with no cfg gate, so
on wasm it implements a method the trait does not declare and omits the one it
does), why nothing on our side can route around it (`mod dropped_file;` is
unconditional in egui-winit's `lib.rs`), and how to re-check: bump it and run
both wasm clippy invocations. `wgpu`'s 29 pin gets a line saying it is a
consequence of the egui tier rather than anything wgpu did.

No dependency change; comments only.

* chore(deps): hold the egui tier in dependabot.yml, not only in a comment

Review made the point that matters: a comment in `Cargo.toml` explains why the
pin exists, and Dependabot cannot read it. It would keep re-opening the same
three PRs every Monday.

The risk is not the noise. It is that the twentieth identical `bump egui from
0.35.0 to 0.36.x` gets merged on the assumption it is routine -- which is exactly
how a pin with a real reason behind it gets undone.

`ignore` entries for egui, egui-wgpu, egui-winit (`>=0.36`) and wgpu (`>=30`),
carrying the failing error and the mechanism, and saying plainly that this is a
HOLD and not a policy: remove all four once upstream ships the one-line cfg, and
re-check by bumping and running both wasm clippy invocations.

Also raised: whether the `ureq` update pulling in `base64` 0.23.1 alongside the
existing 0.22.1 would trip `cargo deny`'s duplicate-version check. Verified
rather than assumed -- `cargo deny check` reports `advisories ok, bans ok,
licenses ok, sources ok`.
@dependabot @github

dependabot Bot commented on behalf of github Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

Looks like egui-wgpu is no longer being updated by Dependabot, so this is no longer needed.

@dependabot dependabot Bot closed this Aug 18, 2026
@dependabot
dependabot Bot deleted the dependabot/cargo/egui-wgpu-0.36.1 branch August 18, 2026 04:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Dependency updates rust Rust / cargo dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant