-
-
Notifications
You must be signed in to change notification settings - Fork 8
Comparing changes
Open a pull request
base repository: jordanlambrecht/tracker-tracker
base: main
head repository: lMortimerl/tracker-tracker
compare: main
- 7 commits
- 12 files changed
- 1 contributor
Commits on Aug 7, 2026
-
fix: detect qBittorrent's renamed session cookie (WebUI 5.2+)
qBittorrent WebUI >= 5.2 renamed its session cookie from SID to QBT_SID_<port> (qbittorrent/qBittorrent#24190). The client hardcoded the SID name both when parsing the login response and when sending the cookie back on every authenticated request, so logins against a 5.2+ instance would fail even with correct credentials. Detect whichever cookie name the server actually sets and thread it through getSession/withSessionRetry into every subsequent request. Also extends sanitizeNetworkError() so auth failures surface as "Authentication failed" instead of a generic, misleading "Connection failed".
Configuration menu - View commit details
-
Copy full SHA for 37fa436 - Browse repository at this point
Copy the full SHA 37fa436View commit details -
feat(trackers): register InfinityHD, TheLeachZone, YU-Scene, and Rock…
…etHD InfinityHD's entry existed on disk but was never wired into the barrel (and still exported the copy-pasted _template.ts name mytracker) so it silently never appeared in the registry. Renamed the export and registered it. Added draft entries for TheLeachZone, YU-Scene, and RocketHD (all UNIT3D) with content categories, seed-time/ratio rules, and banned groups. Left as draft: true — descriptions, colors, and logos aren't sourced yet.
Configuration menu - View commit details
-
Copy full SHA for 5ac51a9 - Browse repository at this point
Copy the full SHA 5ac51a9View commit details -
Merge branch 'fix/qbt-session-cookie'
Fixes qBittorrent WebUI 5.2+ session cookie detection.
Configuration menu - View commit details
-
Copy full SHA for 35c7a73 - Browse repository at this point
Copy the full SHA 35c7a73View commit details -
Merge branch 'feat/tracker-registry-additions'
Registers InfinityHD, TheLeachZone, YU-Scene, and RocketHD.
Configuration menu - View commit details
-
Copy full SHA for c9881b0 - Browse repository at this point
Copy the full SHA c9881b0View commit details -
ci(release): drop Docker Hub push
This fork doesn't have DOCKERHUB_USERNAME/DOCKERHUB_TOKEN secrets configured, and doesn't need Docker Hub distribution — the image is only consumed privately from GHCR. The Docker Hub login step would otherwise fail and block the GHCR push too. GHCR push keeps using the built-in GITHUB_TOKEN, no secrets setup required.
Configuration menu - View commit details
-
Copy full SHA for cb082ca - Browse repository at this point
Copy the full SHA cb082caView commit details -
chore: trigger release workflow
Empty commit — Actions on this fork weren't enabled yet when main was first pushed, so the Release workflow never queued for that push. No content change.
Configuration menu - View commit details
-
Copy full SHA for 4eeece0 - Browse repository at this point
Copy the full SHA 4eeece0View commit details -
fix(ci): lowercase the GHCR image name
docker/build-push-action rejects uppercase repository names, and github.repository preserves the owner's account casing verbatim (lMortimerl/tracker-tracker), which fails buildx with "repository name must be lowercase". Compute IMAGE_NAME with tr instead of using github.repository directly.
Configuration menu - View commit details
-
Copy full SHA for 02ba5f6 - Browse repository at this point
Copy the full SHA 02ba5f6View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...main