From a9f72e34e64e1fd8a350f794b1385c49f65ad715 Mon Sep 17 00:00:00 2001 From: Soispha Date: Sun, 9 Jul 2023 08:09:14 +0200 Subject: [PATCH] Build(cargo): Remove wildcard version specification in `Cargo.toml` Wildcard version is comparable to selecting a version depending on the result of a dice roll. What I mean with this is, that the version will be selected based on what the specific user already has in their cargo registry. This means that the same codebase will compile wonderfully on one machine but will fail with weird errors like: `the trait 'From' is not implemented for 'Input'` on an other one. Additionally crates.io does not accept crates with a bare wildcard version requirement for aforementioned reasons. Lastly using direct versions requirement allows to use `cargo upgrade` to automatically update these requirements to their highest possible value, as determined by SemVer. This works especially well, when adding new dependencies with `cargo add`, as this also adds a direct version requirement. --- Cargo.toml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Cargo.toml b/Cargo.toml index b5f63dd..4c97bff 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -8,12 +8,12 @@ license = "MIT" [dependencies] tui = "0.19" -tui-textarea = { version = "*" } -crossterm = "*" +tui-textarea = { version = "0.2", features = ["crossterm"] } +crossterm = "0.25" matrix-sdk = "0.6" anyhow = "1.0" tokio = { version = "1.0", features = ["macros", "rt-multi-thread"] } tokio-util = "0.7" serde = "1.0" cli-log = "2.0" -indexmap = "*" \ No newline at end of file +indexmap = "2.0.0"