From 5858b53c7907ad93d4c8fe8c188f03b94b3dd087 Mon Sep 17 00:00:00 2001
From: Tomo Suzuki <suztomo@google.com>
Date: Fri, 19 Mar 2021 13:58:38 -0400
Subject: [PATCH] chore(deps): libraries-bom 19.2.1

---
 TROUBLESHOOTING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/TROUBLESHOOTING.md b/TROUBLESHOOTING.md
index 56a478539799..9394973df62b 100644
--- a/TROUBLESHOOTING.md
+++ b/TROUBLESHOOTING.md
@@ -100,7 +100,7 @@ There are different strategies to resolve conflicts, but you must understand the
   least hackish approach, but it is a lot of work that can require multiple releases
    of multiple libraries to sync everything up. 
 - If you can't modify and push new versions of your dependencies, import
-  `com.google.cloud:libraries-bom:19.0.0` (or a more recent version) and use that to
+  `com.google.cloud:libraries-bom:19.2.1` (or a more recent version) and use that to
   select consistent dependency versions. This is the easiest route. 
   For example, this is how you can depend on consistent versions of Guava and 
   `com.google.cloud:google-cloud-storage` without explicitly setting the version of either one:
@@ -112,7 +112,7 @@ There are different strategies to resolve conflicts, but you must understand the
       <dependency>
         <groupId>com.google.cloud</groupId>
         <artifactId>libraries-bom</artifactId>
-        <version>19.0.0</version>
+        <version>19.2.1</version>
         <type>pom</type>
         <scope>import</scope>
        </dependency>