From 9b1125872278e943e800cd3812c0a08e8d84ccad Mon Sep 17 00:00:00 2001
From: Simon Warta <simon@warta.it>
Date: Tue, 5 Sep 2023 00:20:40 +0200
Subject: [PATCH] Require cosmwasm-vm and cosmwasm-std to match cosmwasm-check
 version

---
 CHANGELOG.md              | 12 ++++++++++++
 packages/check/Cargo.toml |  4 ++--
 2 files changed, 14 insertions(+), 2 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index e4123a67dd..1011c1a908 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,18 @@ and this project adheres to
 
 ## [Unreleased]
 
+### Changed
+
+- cosmwasm-check: Use "=" for pinning the versions of cosmwasm-vm and
+  cosmwasm-std dependencies. This ensures that you can use an older version of
+  cosmwasm-check together with the VM of the same version by doing
+  `cargo install cosmwasm-check@1.4.1`. A typical use case would be to check a
+  contract with CosmWasm 1.4, 1.5 and 2.0. Note that other dependencies are
+  still upgraded when using `cargo install` which may lead to API, behavioural
+  or compiler incompatibilities. The
+  [--locked](https://doc.rust-lang.org/cargo/commands/cargo-install.html#dealing-with-the-lockfile)
+  feature allows you use the versions locked when the release was created.
+
 ## [1.4.0] - 2023-09-04
 
 ### Added
diff --git a/packages/check/Cargo.toml b/packages/check/Cargo.toml
index eb12f16401..507eceb8cb 100644
--- a/packages/check/Cargo.toml
+++ b/packages/check/Cargo.toml
@@ -11,8 +11,8 @@ license = "Apache-2.0"
 anyhow = "1.0.57"
 clap = "4"
 colored = "2"
-cosmwasm-vm = { path = "../vm", version = "1.4.0" }
-cosmwasm-std = { path = "../std", version = "1.4.0" }
+cosmwasm-vm = { path = "../vm", version = "=1.4.0" }
+cosmwasm-std = { path = "../std", version = "=1.4.0" }
 
 [dev-dependencies]
 assert_cmd = "=2.0.10" # 2.0.11+ requires Rust 1.65.0 which we currently don't want to make the minimum if possible