Gitea Mirror

Version3.49.0

Source codePublic

Compatible withumbrelOS 0.5 or later

Gitea Mirror automatically mirrors your GitHub repositories to a self-hosted Gitea instance. It supports mirroring public and private repositories, organizations, starred repos, issues, wikis, and pull requests.

Configure your GitHub and Gitea credentials through the web interface to get started. The app will periodically sync your repositories based on your configured schedule.

Key features include:

Mirror repositories from GitHub to Gitea
Support for organizations and starred repositories
Issue and wiki mirroring
Configurable sync intervals and scheduling
Repository cleanup and orphan management
Header-based authentication for reverse proxy SSO

Connecting to Gitea on Umbrel: If you have the Gitea app installed on your Umbrel, use http://gitea_server_1:8085 as the Gitea URL in the mirror settings.

The Gitea Access Token should have the following permissions:

write:repository
read:user
write:organization (optional)

What's new

Version 3.49.0+Oct 30, 2026

⚠️ 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. Key highlights:

Optionally remove attachments from older mirrored releases to reclaim storage. The new "Remove old release assets" setting is off by default; enabling it deletes destination attachments beyond each repository's asset limit, but keeps release notes and tags.
Fix the Activity Log failing to load after a sync records a release-filter warning.
Sort repository owner, organization, and activity name filters alphabetically regardless of case.

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.49.0

Version 3.48.0+Oct 29, 2026

⚠️ 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. Key highlights:

Refresh mirror storage sizes on demand without waiting for a sync.
Pages keep their data while you navigate and refresh in the background.
Large repository and storage lists load and scroll more smoothly.
Release counts, retention limits, and filter previews now include releases beyond the first 30.
Includes a security fix for oversized lists submitted to authenticated MCP tools.

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.48.0

Version 3.47.0+Oct 29, 2026

This update adds a Storage page to show how much space your mirrors use on Gitea and Forgejo. Key highlights:

See total storage, Git and LFS data, release assets, and a breakdown by destination owner and repository.
Search, sort, and filter repositories to find your largest mirrors.
Access the same storage information through the API.

Storage measurements appear as repositories sync after upgrading. Git and LFS sizes trail by one sync. 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.47.0

Version 3.46.0+Oct 26, 2026

This update adds an MCP endpoint and read-only API keys. Key highlights:

Connect MCP clients to inspect mirrors, find failures, add repositories and organizations, and start syncs or retries.
Create read-only API keys for monitoring and integrations that should not change your configuration or mirrors.
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.46.0

Version 3.45.0+Oct 24, 2026

This update improves API integrations and includes security fixes. Key highlights:

Monitor individual repositories and organizations through new API endpoints.
Retrieve existing records when adding an already-tracked repository or organization.
Add organizations without specifying a role, and get clearer errors for invalid API requests.
Includes security updates for Astro and Vite.

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.45.0

Related