From 5cd82b84bb46e911d4465614cb9ee97bddd803a2 Mon Sep 17 00:00:00 2001 From: David Sherret Date: Fri, 28 Oct 2022 11:38:56 -0400 Subject: chore: pin lsp types due to unstable "proposed" feature (#16467) The "proposed" feature that we depend upon in tower-lsp, turns on the "proposed" feature in lsp-types which has breaking changes in patch releases because it's explicitly unstable. We need to pin it to prevent it breaking cargo publish. --- cli/Cargo.toml | 1 + 1 file changed, 1 insertion(+) (limited to 'cli') diff --git a/cli/Cargo.toml b/cli/Cargo.toml index 9fb7e81a2..53216afa0 100644 --- a/cli/Cargo.toml +++ b/cli/Cargo.toml @@ -84,6 +84,7 @@ indicatif = "=0.17.1" jsonc-parser = { version = "=0.21.0", features = ["serde"] } libc = "=0.2.126" log = { version = "=0.4.17", features = ["serde"] } +lsp-types = "=0.93.2" # used by tower-lsp and "proposed" feature is unstable in patch releases mitata = "=0.0.7" monch = "=0.2.1" notify = "=5.0.0" -- cgit v1.2.3