From 993a28b59d4bb82a355c1cb38b5ebf7982b25cdc Mon Sep 17 00:00:00 2001 From: Vika Date: Mon, 16 Dec 2024 12:11:52 +0300 Subject: cargo update, bump minimum libadwaita version to 1.6 I wish there was a way to build against newer libadwaita but be able to gracefully degrade. I heard it's possible in Zig, and `libadwaita` exposes functions to query the underlying library version at runtime, so we might be able to get away with it as long as our build-time environment is new enough... --- Cargo.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Cargo.toml') diff --git a/Cargo.toml b/Cargo.toml index d8f0b34..3e7a242 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -10,7 +10,7 @@ smart-summary = [] default = ["smart-summary"] [dependencies] -adw = { version = "0.7.0", package = "libadwaita", features = ["v1_5"] } +adw = { version = "0.7.0", package = "libadwaita", features = ["v1_6"] } futures = "0.3.30" gettext-rs = { version = "=0.7.0", features = ["gettext-system"] } gio = { version = "0.20.1", features = ["v2_80"] } -- cgit 1.4.1