From 55cb9cf681107cee2f5b353dc5e4ec1fbef728b7 Mon Sep 17 00:00:00 2001
From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com>
Date: Thu, 25 Jun 2020 03:04:10 +0000
Subject: [PATCH] Use `cargo tree` to bump release branch lock files (#10790)
 (#10792)

(cherry picked from commit 48b846203e107a1b6f88c9b9b6e675bb6eeddda7)

Co-authored-by: Trent Nelson <trent@solana.com>
---
 RELEASE.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/RELEASE.md b/RELEASE.md
index bb382e3880..1a978bcbcd 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -116,7 +116,8 @@ There are three release channels that map to branches as follows:
 
 1. After the new release has been tagged, update the Cargo.toml files on **release branch** to the next semantic version (e.g. 0.9.0 -> 0.9.1) with:
      ```
-     scripts/increment-cargo-version.sh patch
+     $ scripts/increment-cargo-version.sh patch
+     $ ./scripts/cargo-for-all-lock-files.sh tree
      ```
 1. Rebuild to get an updated version of `Cargo.lock`:
     ```