From ba14fee18683cdb9254fca52a6d5d305b11c242e Mon Sep 17 00:00:00 2001
From: Predrag Gruevski <2348618+obi1kenobi@users.noreply.github.com>
Date: Wed, 16 Nov 2022 10:31:00 -0500
Subject: [PATCH] Add `--locked` flag to `cargo install` step.

Installing binaries with their locked dependency versions makes it
less likely that you might run into issues caused by bugs in dependency
libraries, since your installed dependency versions match the versions
used in the binary's own test environment.

This is a recommendation that applies to most Rust binary tools. For
example, here's cargo-nextest recommending the same:
https://nexte.st/book/installing-from-source.html#installing-from-cratesio
---
 .github/workflows/ci.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index b5c2eea971c..98858ca8e66 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -217,7 +217,7 @@ jobs:
 
     - uses: Swatinem/rust-cache@359a70e43a0bb8a13953b04a90f76428b4959bb6 # v2.2.0
 
-    - run: cargo install cargo-semver-checks
+    - run: cargo install cargo-semver-checks --locked
     
     - name: Semver Check
       run: cargo semver-checks check-release -p ${{ matrix.crate }}