Make it so our own gpu feature flag controls the sysinfo one, since that's causing the Android build to fail.
Also bumps cross to cross-rs/cross@a9301e9.
Bumps sysinfo to use the newest (breaking) version, 0.40.3. See https://github.com/GuillaumeGomez/sysinfo/blob/main/CHANGELOG.md#0403.
Note I'm not touching the new GPU API here for now. I'm not sure what I'll do on the Linux side as well since I have some fairly tailor-made integrations already, though for other platforms I'll take a look for sure.
This should hopefully address an unsoundness warning from cargo-audit:
```
Crate: rustix
Version: 1.1.4
Warning: unsound
Title: xattr functions mark unwritten bytes as initialized when given a zero-length buffer
Date: 2026-10-27
ID: RUSTSEC-2026-0486
URL: https://rustsec.org/advisories/RUSTSEC-2026-0486
```
This makes it so that if the `.github/workflows` directory is modified, we'll run `zizmor` to check things.
This also fixes some zizmor warnings:
- https://docs.zizmor.sh/audits/#self-repository
- For now, mutes the secret inherits one; this will be fixed later.
Some events weren't blocked when dialog boxes were open, which would mean they would still do stuff behind the dialog (e.g. process actions). This change just blocks it from doing that if the dialog box is open.
Slightly complicated but basically, add some overriding behaviour based on the available width on what string to emit. The main idea is that if we can't fit the percentage sign, we'll first omit that. If it's in decimal mode and we can't fit the decimals too, we then omit the decimals. Finally, if we can't fit the whole number portion, return `None` to hide the column entirely.
Older Windows versions (8.1 and older) were failing to render properly due to winapi not supporting underlining.
Looks like we were transitively enabling this feature because of the crossterm feature, which pulls in ratatui_crossterm which enables it by default. As a quick fix, we manually pull in ratatui_crossterm ourselves and disable that feature.
Adds Windows gnnllvm aarch64 build targets in CI. This applies to the MSI wix build and the normal binary. This also fixes that we weren't specifying the wix build target technically (wasn't a problem though since it was previously just using the default).
This change makes it so that if bracketed paste is not supported (e.g. Windows 7/8), we proceed and don't outright panic. This also has some small cosmetic changes around execute! and cleanup.
https://github.com/rust-lang/rust-clippy/pull/17681 got merged a while ago - this makes it so the `regex_creation_in_loops` clippy `expect` "fails", since it is actually now not triggered.
Unfortunately, this is only in beta from the looks of it at the moment, so I can't just remove it entirely. This change just makes it an unconditional `allow` with a note to get rid of it at some point once it's stable.
Note this only affects macOS, where we use this. This was fine because it's only actually triggered once, and then cached via a `OnceLock`.
Making it so that new features have to go through a feature request first. I'm somewhat not a fan of getting random feature PRs out of the blue - I feel bad saying no too. I would rather be upfront and say that look, if you want a feature, make a feature request and discuss it first before you waste time/tokens/whatever on it.
The way we're doing this for now is:
- If it's less than 100, always show 2 decimal places unless it ends in 0; if so, trim it away
- If it's less than 1000, then do the same but with 1
- If it's over 1000, show no decimal places.
The best way of doing this is probably something like a workspace... but I'm not really in the mood to refactor this into a workspace at the moment, so this will have to do :p