Bump version to 0.11.1

README.md

@@ -57,8 +57,8 @@ This method uses pre-built Docker images and works on minimal hardware specifica
 - Docker installed
 
 ```bash
-# Download install script
-curl -o install.sh https://raw.githubusercontent.com/lanedirt/AliasVault/main/install.sh
+# Download install script from latest stable release
+curl -o install.sh https://raw.githubusercontent.com/lanedirt/AliasVault/0.11.1/install.sh
 
 # Make install script executable and run it. This will create the .env file, pull the Docker images, and start the AliasVault containers.
 chmod +x install.sh

docs/misc/release/create-new-release.md

@@ -13,6 +13,7 @@ Follow the steps in the checklist below to prepare a new release.
 ## Versioning
 - [ ] Update ./src/Shared/AliasVault.Shared.Core/AppInfo.cs and update major/minor/patch to the new version. This version will be shown in the client and admin app footer.
 - [ ] Update ./install.sh `@version` in header if the install script has changed. This allows the install script to self-update when running the `./install.sh update` command on default installations.
+- [ ] Update README.md install.sh download link to point to the new release version
 
 ## Docker Images
 If docker containers have been added or removed:

install.sh

@@ -1,5 +1,5 @@
 #!/bin/bash
-# @version 0.10.3
+# @version 0.11.1
 
 # Repository information used for downloading files and images from GitHub
 REPO_OWNER="lanedirt"

src/Shared/AliasVault.Shared.Core/AppInfo.cs

@@ -30,7 +30,7 @@ public static class AppInfo
     /// <summary>
     /// Gets the patch version number.
     /// </summary>
-    public const int VersionPatch = 0;
+    public const int VersionPatch = 1;
 
     /// <summary>
     /// Gets the build number, typically used in CI/CD pipelines.