Repository navigation
chore(deps)(deps): bump egui from 0.34.3 to 0.35.0 - #212
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [egui](https://github.com/emilk/egui) from 0.34.3 to 0.35.0. - [Release notes](https://github.com/emilk/egui/releases) - [Changelog](https://github.com/emilk/egui/blob/main/CHANGELOG.md) - [Commits](emilk/egui@0.34.3...0.35.0) --- updated-dependencies: - dependency-name: egui dependency-version: 0.35.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
doublegate
added a commit
that referenced
this pull request
Jul 1, 2026
…resh (#215) * chore(deps): bump egui stack 0.34.3 -> 0.35.0 + in-constraint dep refresh Consolidates the three open egui Dependabot PRs (#211 egui-wgpu, #212 egui, #213 egui-winit) into one coordinated bump, since egui/egui-wgpu/egui-winit ship in lockstep and cannot be merged independently, plus a SemVer-compatible refresh of the rest of the transitive graph. egui 0.34.3 -> 0.35.0 (the "Inspection, egui_mcp, classes, improved IME" release) - Verified via crates.io that egui 0.35 stays within the project's *existing* render/windowing tier before touching anything: * egui-wgpu 0.35.0 requires wgpu ^29.0 (locked: 29.0.3) -> no change * egui-winit 0.35.0 requires winit ^0.30.13 (locked: 0.30.13) -> no change * egui 0.35.0 requires accesskit ^0.24.1 (locked: 0.24.1) -> no change So there is NO wgpu / winit / accesskit / naga movement; this is a pure in-tier bump and the shipped / native / no_std / wasm builds stay behavior-equivalent. - Migrated the one API break introduced by 0.35: egui::Panel::show_inside was deprecated and renamed to Panel::show(ui, ..) (same &mut Ui-nesting signature). Updated the three call sites -- the shell menu bar and status bar (ui_shell.rs) and the documentation side panel (debugger/doc_panel.rs) -- and refreshed the three surrounding architecture comments (ui_shell.rs + debugger/mod.rs) that named the old method, keeping the docs in sync with the code per the docs-as-spec rule. - The transitive font stack epaint 0.35 pulls in (fearless_simd, read-fonts, skrifa, vello_*) moved with it; ecolor/emath/epaint/epaint_default_fonts all advanced 0.34.3 -> 0.35.0 in lockstep. In-constraint transitive refresh (cargo update; SemVer-compatible only) - Picked up ~20 patch/minor bumps that violate no manifest requirement: anyhow 1.0.103, bstr 1.12.3, camino 1.2.4, clap_complete 4.6.7, console 0.16.4, js-sys / web-sys 0.3.103, rustls-pki-types 1.15.0, time 0.3.53, uuid 1.23.4, wasm-bindgen 0.2.126 (+ the -futures/-macro/-shared satellites), zlib-rs 0.6.5, and others. - wasm-bindgen 0.2.125 -> 0.2.126 required mirroring the pin in crates/rustynes-frontend/web/Trunk.toml: the wasm-bindgen library and the trunk-invoked wasm-bindgen CLI are released in lockstep and version-check each other, so a mismatch would fail `trunk build` (and the GitHub Pages deploy) at the wasm-bindgen step even though wasm clippy still passes. Deliberately EXCLUDED (out-of-tier / breaking; each needs its own change) - wgpu 30 / naga 30 -- would break the egui-wgpu 0.35 render tier (pins wgpu ^29). - getrandom 0.4 -- breaking wasm backend API; its `js` feature is obsolete. - uniffi 0.32 -- the mobile UniFFI bridge; needs a Kotlin/Swift regen plus an on-device verification pass, not a desktop drop-in. Verification (all green locally) - cargo fmt --all --check: clean. - cargo clippy --workspace --all-targets -- -D warnings: clean. - cargo clippy -p rustynes-frontend --features full -- -D warnings: clean. - wasm32 clippy (wasm-winit default + wasm-canvas): clean. - RUSTDOCFLAGS=-D warnings cargo doc --workspace --no-deps: clean. - cargo test -p rustynes-frontend: 431 passed, 0 failed. - AccuracyCoin 139/139 unaffected -- the deterministic #![no_std] chip stack is untouched and byte-identical; egui lives only in the host frontend. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * chore(deny): ignore RUSTSEC-2026-0192 (ttf-parser unmaintained, transitive via winit) The "Cargo Deny Check" CI gate went red on the advisories pass with RUSTSEC-2026-0192 — `ttf-parser` flagged unmaintained. This is an informational "unmaintained" advisory, NOT an exploitable vulnerability, on a purely transitive dependency the workspace cannot influence from its manifest: winit 0.30.13 -> sctk-adwaita -> ab_glyph -> owned_ttf_parser -> ttf-parser 0.25.1 ttf-parser 0.25.1 is already the latest release; the only way off it is for winit's Wayland client-side-decoration stack to drop ab_glyph, which is outside our control until a future winit bump. Crucially this is NOT introduced by the egui 0.34->0.35 bump in this PR: `main` carries the identical `ttf-parser 0.25.1`, and cargo-deny fetches the live RUSTSEC database at check time, so the freshly-published advisory fails equally on `main` — this PR is simply the first to re-run the security workflow (which is path-filtered to Cargo.toml/lock changes) after the advisory landed. Per deny.toml's own stated policy ("a real transitive advisory with no safe upgrade"), added RUSTSEC-2026-0192 to the `[advisories].ignore` list with a comprehensive comment recording the dependency chain, why it is safe (unmaintained != vulnerable), and the revisit condition (a winit bump that drops the ab_glyph/ttf-parser chain). `bans`/`licenses`/`sources` were already green and are unaffected; no real vulnerability is being suppressed. Verified locally: `cargo deny check` -> "advisories ok, bans ok, licenses ok, sources ok". Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
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
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.
Bumps egui from 0.34.3 to 0.35.0.
Release notes
Sourced from egui's releases.
... (truncated)
Changelog
Sourced from egui's changelog.
... (truncated)
Commits
f72eaf6Add egui_inspection to missing places6f15dc0Release 0.35.0bc50ef7Fix accidental change9758f7bFix video74c0a0cAdd changeloga08630cImprove docs on some methods to clarify what counts as a "click" (#8251)5bf62caImplement proper visuals for IME composition (#8083)a8d09ebFix macOS wgpu live resize with low-latency surfaces (#8229)2e26b70Calllogiceven while browser tab is in background (#8257)26ead4afeat: addremove_string()to storage trait (#8264)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)