Dawnsorrow/HS-Rename
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 16 Wiki Activity

Release v1.0.4: fix TheTVDB search ID parsing.

Browse Source 
Parse series-76320 style search hits from TheTVDB v4, document Gear Lever Forgejo setup, and adjust AppImage build metadata for update detection.

Co-authored-by: Cursor <[email protected]>
This commit is contained in:
Bulk Renamer
2026-07-03 17:17:49 -05:00
co-authored by Cursor
parent b3ce276d1b
commit db460fb9b3
6 changed files with 96 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/GEARLEVER.md
+48 -39
View File
@@ -1,58 +1,67 @@
# Using HSRename with Gear Lever
[Gear Lever](https://github.com/mijorus/gearlever) can manage and update the HSRename AppImage. Because releases are hosted on **Gitea** (not GitHub), use one of the options below.
[Gear Lever](https://github.com/mijorus/gearlever) 4.x can update HSRename from Gitea releases. Gitea uses the same API as **Forgejo**, which Gear Lever supports directly.
## Option 1: Custom update URL (recommended to try first)
## Important: use Forgejo, not Default
Gitea uses the same release path style as GitHub:
`/owner/repo/releases/download/{tag}/{filename}`
In the HSRename details screen:
1. Open **Gear Lever** and add the HSRename AppImage (drag & drop or **Add**).
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):
```
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.
- **Source** must be **Forgejo** (not `Default`).
- The **Website** field is only metadata. It does **not** check for updates.
- Do **not** paste the release download URL into Website.
If your Gear Lever only supports GitHub-style URLs and rejects this, use Option 2.
## Configure updates (Gear Lever 4+)
## Option 2: Static URL (manual update link)
1. Open **Gear Lever** → select **HSRename**.
2. Set **Source** to **Forgejo**.
3. Fill in:
If the wildcard URL does not work:
| Field | Value |
|-------|--------|
| **Repo URL** | `https://git.hisora.dev/Dawnsorrow/HS-Rename` |
| **Release file name** | `HSRename.AppImage` |
| **Allow pre-releases** | Off (unless you want draft releases) |
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.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**.
4. Save, then use **Check for updates** / **List updates**.
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.
If the fields validate (no error), Gear Lever queries:
## Option 3: CLI (if you use Gear Lever from the terminal)
`https://git.hisora.dev/api/v1/repos/Dawnsorrow/HS-Rename/releases/latest`
After adding the AppImage in Gear Lever, you can set the update URL from the command line:
and compares the release asset size with your local AppImage.
```bash
# Set custom update URL (try the wildcard pattern)
gearlever --set-update-url /path/to/HSRename.AppImage "https://git.hisora.dev/Dawnsorrow/HS-Rename/releases/download/*/HSRename.AppImage"
## Direct download URL pattern
# Check for updates
gearlever --list-updates
# Apply update
gearlever --update /path/to/HSRename.AppImage
```
Replace `/path/to/HSRename.AppImage` with the actual path where Gear Lever stores the AppImage.
## Release download URL pattern
For any release tag `vX.Y.Z`, the direct download URL is:
For release tag `vX.Y.Z`:
```
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.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).
Latest release today:
```
https://git.hisora.dev/Dawnsorrow/HS-Rename/releases/download/v1.0.3/HSRename.AppImage
```
## Fallback: Static URL
If Forgejo does not work in your Gear Lever build, set **Source** to **Static URL** and paste the **exact** URL of the newest release (update this manually each release):
```
https://git.hisora.dev/Dawnsorrow/HS-Rename/releases/download/v1.0.3/HSRename.AppImage
```
## CLI (if `gearlever` is installed)
Gear Lever 4 may use different CLI options than older docs. Prefer the GUI Forgejo fields above. If your install still supports `--set-update-url`, the old wildcard pattern is **not** reliable for self-hosted Gitea; use Forgejo instead.
## Troubleshooting
| Symptom | Likely cause |
|---------|----------------|
| No update offered | Source is still **Default**, or local file is already the latest release (same size as `releases/latest`). |
| URL looks truncated in Website | Website is cosmetic only; configure **Forgejo** fields instead. |
| Update never finds newer builds | Wrong repo URL, wrong filename, or release has no `HSRename.AppImage` asset attached. |
Releases page: https://git.hisora.dev/Dawnsorrow/HS-Rename/releases