github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-07 12:37:43 -05:00
Code Issues 103 Packages Projects Releases 93 Wiki Activity

[PR #150] [MERGED] fix: Detect and recreate incorrectly ordered releases (#148) #1049

New Issue
Closed
opened 2026-04-19 13:37:43 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-19 13:37:43 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/RayLabsHQ/gitea-mirror/pull/150
Author: @arunavo4
Created: 11/8/2025
Status: ✅ Merged
Merged: 11/8/2025
Merged by: @arunavo4

Base: main ← Head: 148-release-order-again

📝 Commits (1)

  • e951e97 fix: Detect and recreate incorrectly ordered releases (#148)

📊 Changes

1 file changed (+109 additions, -16 deletions)

View changed files

📝 src/lib/gitea.ts (+109 -16)

📄 Description

This fix addresses the persistent release ordering issue by detecting when existing releases in Gitea are in the wrong chronological order and automatically deleting and recreating them in the correct order.

Root Cause:

  • Gitea ALWAYS sorts releases by created_unix DESC, id DESC
  • The Gitea API provides NO way to set created_unix when creating releases
  • Previous fix (PR #146) only worked for NEW releases, not UPDATES
  • When releases are UPDATED, their created_unix timestamp doesn't change
  • So releases created in wrong order initially stayed wrong forever

Solution:
Before processing releases, the code now:

  1. Fetches all existing releases from Gitea
  2. Checks if they're in correct chronological order
  3. If order is wrong: deletes all releases and recreates them in correct order
  4. If order is correct: proceeds with normal update logic

How it works:

  • Maps each release to its expected chronological index (0=oldest, n=newest)
  • Checks if Gitea's releases (sorted by created_unix DESC) match expected order
  • Detects mis-ordering by comparing adjacent releases
  • Logs detailed information about ordering issues found
  • Deletes and recreates only when necessary (optimized)

User Impact:

  • Users who mirrored repos BEFORE PR #146: ordering will be fixed on next mirror
  • First-time mirrors: work correctly (as before)
  • Subsequent mirrors: verify order and fix if needed
  • No manual intervention required

Fixes #148
Related: #129, PR #146

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/RayLabsHQ/gitea-mirror/pull/150 **Author:** [@arunavo4](https://github.com/arunavo4) **Created:** 11/8/2025 **Status:** ✅ Merged **Merged:** 11/8/2025 **Merged by:** [@arunavo4](https://github.com/arunavo4) **Base:** `main` ← **Head:** `148-release-order-again` --- ### 📝 Commits (1) - [`e951e97`](https://github.com/RayLabsHQ/gitea-mirror/commit/e951e97790efb8fcee4c1852479a11520dfa607b) fix: Detect and recreate incorrectly ordered releases (#148) ### 📊 Changes **1 file changed** (+109 additions, -16 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/gitea.ts` (+109 -16) </details> ### 📄 Description This fix addresses the persistent release ordering issue by detecting when existing releases in Gitea are in the wrong chronological order and automatically deleting and recreating them in the correct order. **Root Cause:** - Gitea ALWAYS sorts releases by `created_unix DESC, id DESC` - The Gitea API provides NO way to set `created_unix` when creating releases - Previous fix (PR #146) only worked for NEW releases, not UPDATES - When releases are UPDATED, their `created_unix` timestamp doesn't change - So releases created in wrong order initially stayed wrong forever **Solution:** Before processing releases, the code now: 1. Fetches all existing releases from Gitea 2. Checks if they're in correct chronological order 3. If order is wrong: deletes all releases and recreates them in correct order 4. If order is correct: proceeds with normal update logic **How it works:** - Maps each release to its expected chronological index (0=oldest, n=newest) - Checks if Gitea's releases (sorted by created_unix DESC) match expected order - Detects mis-ordering by comparing adjacent releases - Logs detailed information about ordering issues found - Deletes and recreates only when necessary (optimized) **User Impact:** - Users who mirrored repos BEFORE PR #146: ordering will be fixed on next mirror - First-time mirrors: work correctly (as before) - Subsequent mirrors: verify order and fix if needed - No manual intervention required Fixes #148 Related: #129, PR #146 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-19 13:37:43 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#1049
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?