From 682e76de2f71f0e6a03bf1aad3d6754943dce8b6 Mon Sep 17 00:00:00 2001
From: Bulk Renamer <bulk-renamer@local>
Date: Fri, 3 Jul 2026 16:57:25 -0500
Subject: [PATCH] Update Gitea URLs to git.hisora.dev/Dawnsorrow/HS-Rename.

Align release script, Gear Lever docs, and remote with the new host and repo name.

Co-authored-by: Cursor <cursoragent@cursor.com>
---
 docs/GEARLEVER.md | 14 +++++++-------
 release_gitea.sh  |  2 +-
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/GEARLEVER.md b/docs/GEARLEVER.md
index 104cf44..1415649 100644
--- a/docs/GEARLEVER.md
+++ b/docs/GEARLEVER.md
@@ -11,7 +11,7 @@ Gitea uses the same release path style as GitHub:
 2. Select the HSRename entry and open **Update** / **Custom update URL** (or the equivalent in your Gear Lever version).
 3. Try this URL pattern (with a wildcard for the tag):
    ```
-   http://brassnet.ddns.net:33983/Dawnsorrow/HS-Rename/releases/download/*/HSRename.AppImage
+   https://git.hisora.dev/Dawnsorrow/HS-Rename/releases/download/*/HSRename.AppImage
    ```
 4. If Gear Lever accepts it (e.g. field turns green or validates), it may use the Gitea releases page to resolve the latest tag and offer updates when you push new releases.
 5. Use **Check for updates** / **List updates** to see if it detects new versions.
@@ -24,9 +24,9 @@ If the wildcard URL does not work:
 
 1. In Gear Lever, add HSRename and set **Update** to **Static URL**.
 2. Paste the **direct download URL** of the current release, for example:
-   - **v1.0.1:**  
-     `http://brassnet.ddns.net:33983/Dawnsorrow/HS-Rename/releases/download/v1.0.1/HSRename.AppImage`
-3. When a new version is released (e.g. v1.0.2), open the [releases page](http://brassnet.ddns.net:33983/Dawnsorrow/HS-Rename/releases), open the new release, right‑click **HSRename.AppImage** → **Copy link address**, then in Gear Lever set the Static URL to that new link and run **Update**.
+   - **v1.0.3:**  
+     `https://git.hisora.dev/Dawnsorrow/HS-Rename/releases/download/v1.0.3/HSRename.AppImage`
+3. When a new version is released (e.g. v1.0.4), open the [releases page](https://git.hisora.dev/Dawnsorrow/HS-Rename/releases), open the new release, right‑click **HSRename.AppImage** → **Copy link address**, then in Gear Lever set the Static URL to that new link and run **Update**.
 
 So: Gear Lever will only “see” updates if you change the Static URL to the new release’s download link when you want to update.
 
@@ -36,7 +36,7 @@ After adding the AppImage in Gear Lever, you can set the update URL from the com
 
 ```bash
 # Set custom update URL (try the wildcard pattern)
-gearlever --set-update-url /path/to/HSRename.AppImage "http://brassnet.ddns.net:33983/Dawnsorrow/HS-Rename/releases/download/*/HSRename.AppImage"
+gearlever --set-update-url /path/to/HSRename.AppImage "https://git.hisora.dev/Dawnsorrow/HS-Rename/releases/download/*/HSRename.AppImage"
 
 # Check for updates
 gearlever --list-updates
@@ -52,7 +52,7 @@ Replace `/path/to/HSRename.AppImage` with the actual path where Gear Lever store
 For any release tag `vX.Y.Z`, the direct download URL is:
 
 ```
-http://brassnet.ddns.net:33983/Dawnsorrow/HS-Rename/releases/download/vX.Y.Z/HSRename.AppImage
+https://git.hisora.dev/Dawnsorrow/HS-Rename/releases/download/vX.Y.Z/HSRename.AppImage
 ```
 
-So when we push a new release (e.g. v1.0.2), that new tag’s URL is what Gear Lever needs (either via the wildcard in Option 1 or by pasting the new URL in Option 2).
+So when we push a new release (e.g. v1.0.4), that new tag’s URL is what Gear Lever needs (either via the wildcard in Option 1 or by pasting the new URL in Option 2).
diff --git a/release_gitea.sh b/release_gitea.sh
index b2044be..05eedba 100755
--- a/release_gitea.sh
+++ b/release_gitea.sh
@@ -9,7 +9,7 @@
 set -euo pipefail
 cd "$(dirname "$0")"
 
-GITEA_HOST="${GITEA_HOST:-http://brassnet.ddns.net:33983}"
+GITEA_HOST="${GITEA_HOST:-https://git.hisora.dev}"
 GITEA_OWNER="${GITEA_OWNER:-Dawnsorrow}"
 GITEA_REPO="${GITEA_REPO:-HS-Rename}"
 APP_IMAGE="HSRename.AppImage"