Dependency Dashboard

[renovate[bot]]

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• [ ] chore(deps): update actions/setup-python action to v5

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• [ ] chore(deps): update rust crate wgpu to 0.20
• [ ] chore(deps): update rust crate winit to 0.30
• [ ] fix(deps): update rust crate html5ever to 0.27
• [ ] fix(deps): update rust crate ndk to 0.9
• [ ] fix(deps): update rust crate ndk-sys to 0.6
• [ ] fix(deps): update rust crate soup3 to 0.6
• [ ] fix(deps): update rust crate windows to 0.58
• [ ] fix(deps): update rust crate windows-core to 0.58
• [ ] Click on this checkbox to rebase all open PRs at once

Detected dependencies

cargo

Cargo.toml

- `tracing 0.1` - `once_cell 1` - `thiserror 1.0` - `http 1.1` - `raw-window-handle 0.6` - `dpi 0.1` - `pollster 0.3.0` - `tao 0.28` - `wgpu 0.19` - `winit 0.29` - `getrandom 0.2` - `http-range 0.1` - `percent-encoding 2.3` - `javascriptcore-rs =1.1.2` - `webkit2gtk =2.0.1` - `webkit2gtk-sys =2.0.1` - `gtk 0.18` - `soup3 0.5` - `x11-dl 2.21` - `gdkx11 0.18` - `percent-encoding 2.3` - `webview2-com 0.31` - `windows-version 0.1` - `windows-core 0.57` - `dunce 1` - `windows 0.57` - `block 0.1` - `cocoa 0.25` - `core-graphics 0.23` - `objc 0.2` - `objc_id 0.1` - `crossbeam-channel 0.5` - `html5ever 0.26` - `kuchiki 0.8` - `sha2 0.10` - `base64 0.22` - `jni 0.21` - `ndk 0.7` - `ndk-sys 0.4` - `ndk-context 0.1` - `tao-macros 0.1` - `libc 0.2`

bench/Cargo.toml

- `anyhow 1.0` - `time 0.3` - `tempfile 3.10` - `serde_json 1.0` - `serde 1.0`

github-actions

.github/workflows/audit.yml

- `actions/checkout v4` - `rustsec/audit-check v1`

.github/workflows/bench.yml

- `actions/checkout v4` - `actions/setup-python v4` - `Swatinem/rust-cache v2` - `actions/checkout v4`

.github/workflows/build.yml

- `actions/checkout v4` - `Swatinem/rust-cache v2` - `actions/checkout v4`

.github/workflows/clippy-fmt.yml

- `actions/checkout v4` - `actions/checkout v4`

.github/workflows/covector-comment-on-fork.yml

.github/workflows/covector-status.yml

- `actions/checkout v4`

.github/workflows/covector-version-or-publish.yml

- `actions/checkout v4` - `tauri-apps/create-pull-request v3`

---

• [ ] Check this box to trigger a request for Renovate to run again on this repository

[rhysd]

What is an issue on upgrading gtk crate to v0.18? Today I tried to upgrade rfd to the latest but I couldn't do it due to the incompatibility of the crate (wry requested v0.16 and rfd requested v0.18). And v0.16 was released almost one year ago so it looks outdated.

[wusyong]

Hey sorry I planned to update the version this month but my framework laptop was broken. I'm reaching to one of working group member to update all the dependencies. There are a few gtk crates need to update their gir and gtk version first:

• https://github.com/tauri-apps/webkit2gtk-rs
• https://github.com/tauri-apps/javascriptcore-rs
• https://github.com/tauri-apps/libappindicator-rs And then we can update tao and wry accordingly.

[dklassic]

While attempting to upgrade gtk version for javascriptcore-rs, seems like gtk v0.18 requires the crate cfg-expr v0.15.5 which requires rustc version to be 1.70.0 or newer. @amrbashir , @FabianLars , is it okay to bump our Rust version for this?

[FabianLars]

That's indeed quite steep and also the reason why we're always so slow to upgrade the gtk crates. The last times they also updated their msrv to the latest rust version available at that point :/

Anyway, we didn't really talk about the new msrv policy in v2 yet but i still believe we'll go with something like the last 3 versions / the last 6 months (same thing with current release schedule). This would mean gtk 0.18 would have to wait until December though. We could make an exception for tauri alpha&beta and apply the msrv policy only the to then stable release 🤔

I guess it's time for a proper msrv policy talk/decision including crates like webkitgtk-rs that are also used in the rust ecosystem and not just us. Edit: And with the last point updating the msrv of these crates would have been fine if webkitgtk would still be 0.x since we could just stick to an older version in wry, now i have no idea how to handle gtk updates as a whole since they are part of the public api (re-export of glib & gio) which means updating them would be a breaking change.

[wusyong]

@FabianLars Waiting until December is too long. Do we force MSRV on alpha at the moment? If not, I think we could start updating it.

[rhysd]

Thank you for the answer to my question. I understood that gtk-rs is aggressive on updating MSRV and it is hard to handle. And I appreciate the work to keep dependencies and MSRV by tauri developers. I'll try to keep my dependencies to be compatible with current gtk-rs crate which wry depends on.

[FabianLars]

@ FabianLars Waiting until December is too long. Do we force MSRV on alpha at the moment? If not, I think we could start updating it.

Well, we've never explicitly talked about it. So far we were still really hesitant to raise the msrv but still did it a few times. But like I said, we should have a dedicated msrv policy discussion asap!

As an interim solution i personally think it's okay to raise the msrv to whatever in the alpha versions but it could easily backfire if the policy discussion ends up deciding on something longer than "last 3 releases". We can of course also just not update webkitgtk etc in tauri and/or wry if needed, so that at other crate consumers can upgrade gtk.

[wusyong]

Looks like gtk3 won't bump any version any time soon: https://gtk-rs.org/blog/2023/08/28/new-release.html I would say it's safe to update then. At the meantime, I'll discuss with other member about our MSRV policy.