Update gitea-mirror to v3.54.0

This commit is contained in:
Kai Chappel authored and GitHub committed 2026-11-17 12:56:08 +00:00
1 parent 0cfe3ed099
commit 3a5c528aee
2 files changed
+10 -26

No files matched your search

+1 -1
View File
@@ -7,7 +7,7 @@ services:
APP_PORT: 4321
web:
image: ghcr.io/raylabshq/gitea-mirror:v3.53.0@sha256:4c6c9a1c379060385ed1d0bc5dfd44108b8d4683c58c3b35597649b2b79e180e
image: ghcr.io/raylabshq/gitea-mirror:v3.54.0@sha256:be5600216ff8a152ea7ddd9152c68cc94b56886e85bf44fe67853ee1bcac2ada
restart: on-failure
user: "1000:1000"
volumes:
+9 -25
View File
@@ -5,7 +5,7 @@ storage:
name: Gitea Mirror
tagline: Mirror your GitHub repositories to a Gitea instance automatically
category: developer
version: "3.53.0"
version: "3.54.0"
port: 4322
description: >-
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.
@@ -44,35 +44,19 @@ defaultUsername: ""
defaultPassword: ""
dependencies: []
releaseNotes: >-
This update adds beta support for mirroring repositories from any Git host with an HTTP or HTTPS clone URL. Add repositories individually on the Repositories page; branches and tags are mirrored, but organizations, releases, issues, and SSH remotes are not supported. Use the Always Backup snapshot strategy to protect these mirrors against rewritten history.
🔒 Saved source, destination, and notification secrets are now hidden from configuration and source API responses, including read-only API keys. Scripts that read these endpoints must keep their own credentials. Leaving a secret blank preserves it; changing its scheme, host, or port requires entering a new token.
GitLab listings can optionally start with a smaller batch using GITLAB_PAGE_SIZE (10–100, default 100) for slow servers. Automatic batch reduction remains enabled.
SSO now restricts new accounts and account linking to the provider's configured email domain. If you use SSO, check that each provider's Domain is your users' email domain, not the provider's hostname. Existing SSO users are unaffected.
🔒 Includes Astro security fixes for image-endpoint file access and dynamic-tag attribute injection.
Settings no longer reset at restart when credentials are set through environment variables. Large release assets now stream through temporary files instead of consuming excessive memory; keep enough free app-data space for the largest asset. Long-running initial imports are also handled more reliably.
🔒 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.
Back up data/gitea-mirror.db and your Gitea or Forgejo instance before upgrading, especially when skipping older versions. Release retention and filters inspect all destination releases and can delete older or excluded releases on the next sync. Preview tag rules before enabling filters. Optional attachment pruning also deletes attachments beyond the configured limit.
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.
Earlier security fixes prevent source-token exposure and unsafe redirects or private-address downloads for externally linked Forgejo assets. If you mirror untrusted Forgejo repositories with a token, rotate that source token. External assets are limited to 512 MB and 15 minutes; larger or slower assets are skipped.
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.
If updating from before 3.50.0, disabling issue media removes it from mirrored issue bodies on their next sync; existing comments keep it. GitHub App-backed mirrors require Gitea 1.27 or later and Gitea Mirror's scheduler; use personal access tokens with older Gitea, Forgejo, starred repositories, or star lists.
⚠️ 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.
New configurations start with scheduling off unless enabled through environment variables. Repository cleanup no longer automatically archives or deletes destination copies when a source disappears. If updating from before 3.17 and using registered OAuth provider clients, rotate each client secret after upgrading.
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.
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.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.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.53.0
Full release notes can be found at https://github.com/RayLabsHQ/gitea-mirror/releases/tag/v3.54.0
path: ""