From b30ed3ae4eddbcdddfcf28e37b490dca15212f78 Mon Sep 17 00:00:00 2001
From: placeholderphone <jacksonh.dot@gmail.com>
Date: Sun, 7 Dec 2025 17:50:37 -0800
Subject: [PATCH] Bump VaultAPI version to 1.7.1

Updated VaultAPI version from 1.7 to 1.7.1 in dependencies.
---
 README.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index d50c704..413864d 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ How to include the API with Maven:
     <dependency>
         <groupId>com.github.MilkBowl</groupId>
         <artifactId>VaultAPI</artifactId>
-        <version>1.7</version>
+        <version>1.7.1</version>
         <scope>provided</scope>
     </dependency>
 </dependencies>
@@ -24,12 +24,10 @@ repositories {
     maven { url 'https://jitpack.io' }
 }
 dependencies {
-    compileOnly "com.github.MilkBowl:VaultAPI:1.7"
+    compileOnly "com.github.MilkBowl:VaultAPI:1.7.1"
 }
 ```
 
-**Note**: The VaultAPI version has 2 numbers (major.minor), unlike Vault, which has 3. The 2 numbers in the VaultAPI will always correspond to the 2 beginning numbers in a Vault version to make it clear what versions your plugin will for sure work with.
-
 ## Why Vault?
 I have no preference which library suits your plugin and development efforts
 best.  Really, I thought a central suite (rather...Vault) of solutions was the