🔧 Critical Fix for Releases Mirroring
This patch completes the authentication fixes from v3.2.4, specifically addressing the releases mirroring function that was accidentally missed in the previous update.
What Was Still Broken in v3.2.4
Users reported that after v3.2.4, they were still seeing:
[HTTP Client] Authentication failed for .../repos/starred/AdrenoToolsDrivers/releases
[HTTP Client] Response: {"message":"user does not exist [uid: 0, name: ]"}
Root Cause
The mirrorGitHubReleasesToGitea function was using encrypted tokens directly instead of decrypting them first. While v3.2.4 fixed this for issues, PRs, labels, and milestones, the releases function was missed.
What's Fixed
🔐 Authentication
- Fixed releases mirroring function now properly decrypts tokens before API calls
- Fixed "user does not exist [uid: 0]" error specifically for GitHub releases synchronization
- Added repository existence verification before attempting to mirror releases
✨ Improvements
- Duplicate detection - Skips releases that already exist to prevent errors on re-runs
- Better error handling - Individual release failures don't stop the entire process
- Enhanced logging - Clear
[Releases]prefix for debugging release operations
📦 Docker Image
docker pull ghcr.io/raylabshq/gitea-mirror:3.2.5
docker pull ghcr.io/raylabshq/gitea-mirror:latest💡 Upgrade Notes
If you're experiencing authentication errors with releases after v3.2.4, this update will resolve them. No configuration changes needed - just update to v3.2.5.
🙏 Acknowledgments
Thanks to the users who provided detailed logs after testing v3.2.4, which helped identify that the releases function was still affected.
Full Changelog: v3.2.4...v3.2.5