Failed mirror creation now includes the reason reported by Gitea or Forgejo, rather than only an HTTP status. The Dashboard also links to destination repositories while they are mirroring or syncing, and for archived repositories.
GitLab imports are fast again on responsive instances while still adapting to slow servers. Listings start with larger batches and automatically reduce the batch size after a timeout, continuing from the same position. No configuration changes are needed.
This update fixes backup configuration handling, including disabled backups being re-enabled on restart when using environment-based configuration. Existing configurations keep their saved backup settings; change them on the Configuration page.
It also fixes database selection for custom deployments with a non-SQLite database URL. The standard Umbrel package already uses the supported SQLite path and needs no configuration changes.
š This update also includes the earlier security fix that prevents externally linked Forgejo release assets from exhausting the mirror's memory. Linked downloads are limited to 512 MB and 15 minutes; assets exceeding either limit are skipped with a warning. Assets hosted directly by the source have no size cap.
Release asset downloads now stop after two minutes without receiving data instead of leaving a sync stuck indefinitely. Failed downloads are retried on the next sync.
This update also includes the previous security fixes for source-token exposure when mirroring externally linked Forgejo release assets, requests to private addresses, and destination tokens following redirects to another host.
If you mirror releases from a Forgejo source such as Codeberg using a token and mirror repositories you do not fully trust, rotate that source token. Externally linked assets on private or local addresses are now skipped with a warning.
ā ļø Back up your Gitea or Forgejo instance and review release limits and filters before upgrading. The next sync can delete older releases: retention and release filters now inspect all destination releases, not just the newest 30. Previously untrimmed releases beyond your limit or excluded by your filters will be removed.
If you're updating from a version older than 3.51.1:
- Mirrors interrupted by a gateway timeout now finish syncing releases, issues, and other metadata instead of appearing complete with missing content. Imports still running in Gitea are given up to 30 minutes to finish before continuing.
- Release assets from private GitHub repositories now download correctly. These downloads use GitHub's API quota and pause when the rate limit is reached.
If a repository is already missing releases after a timeout, its next sync will catch up. With scheduling off, press Sync. Pressing Mirror on a repository already in Gitea now performs a full sync and ends with a synced status.
If you're updating from a version older than 3.51.0, you can also get Activity Log warnings and optional notifications when a requested mirror sync has stalled for over an hour. This covers syncs requested by Gitea Mirror, not mirrors running only on Gitea's own schedule.
If you're updating from a version older than 3.50.0, you can also filter GitHub issues by state, optionally skip comments or media, and filter repositories by destination owner. Disabling media removes it from mirrored issue bodies on their next sync; existing comments keep their media.
If you're updating from a version older than 3.49.0, you can also optionally remove attachments from older mirrored releases to reclaim storage. This setting is off by default; enabling it deletes attachments beyond each repository's asset limit while keeping release notes and tags. The Activity Log also loads correctly after release-filter warnings.
If you're updating from a version older than 3.48.0, you can also refresh storage sizes on demand, navigate between cached pages, and browse large lists more smoothly. Release retention and filters now inspect every destination release, and authenticated MCP tools include a security fix for oversized lists.
If you're updating from a version older than 3.47.0, the Storage page also shows total storage and a breakdown by owner and repository. GitHub and GitLab push destinations are not measured.
If you're updating from a version older than 3.46.0, Gitea Mirror also includes an MCP endpoint and read-only API keys. Existing API keys keep full access.
Reminder: release filters added in 3.44.0 delete already-mirrored releases that no longer match on the next sync. Preview the affected releases in the tag rules dialog before saving, and back up your Gitea instance. Existing configurations keep mirroring all releases until you enable a filter.
If you're updating from a version older than 3.42.0, GitHub App installation authentication is also available as an alternative to personal access tokens. GitHub App-backed mirrors require Gitea 1.27 or later. Keep Gitea Mirror's scheduler enabled for these mirrors, as Gitea's independent pull schedule is disabled. Use personal access tokens with older Gitea versions, Forgejo, starred repositories, or star lists. Existing token-based mirrors are unchanged.
If you're updating from a version older than 3.40.4, milestone assignments are now mirrored for issues and pull requests. Existing unchanged items receive their assignments on the next weekly full sync; changed items receive them on their next sync.
If you're updating from a version older than 3.40.1, Gitea Mirror also includes improved GitHub rate-limit handling, an organizations list view, incremental scheduled issue and pull request syncs, and saved URL/security hardening.
If you're updating from a version older than 3.36.2, Gitea Mirror also includes scheduling, organization ignore/include, and destination display fixes. Existing configurations are not touched. New configurations start with scheduling off unless SCHEDULE_ENABLED=true, SCHEDULE_INTERVAL, or GITEA_MIRROR_INTERVAL enables it.
If you're updating from a version older than 3.36.1, Gitea Mirror also includes fixes for duplicate release assets, organization destination overrides, crash recovery, duplicate source-row scheduling/import behavior, and progress checkpoint handling.
If you're updating from a version older than 3.34.0, Gitea Mirror also adds organization source pins and earlier multi-source database migrations. Back up data/gitea-mirror.db and your Gitea or Forgejo instance before upgrading.
Reminder for users updating from 3.27.1 or older: repository cleanup no longer archives or deletes copies in Gitea or Forgejo automatically when the original GitHub repository is no longer found.
If you're updating from a version older than 3.17 and use OAuth provider clients registered in Gitea Mirror, rotate the client secret for each client after upgrading because OAuth application secrets are stored hashed after migration.
Full release notes can be found at https://github.com/RayLabsHQ/gitea-mirror/releases/tag/v3.51.8