diff --git a/gitea-mirror/docker-compose.yml b/gitea-mirror/docker-compose.yml index 18d85e7e3..b0c7f8e8e 100644 --- a/gitea-mirror/docker-compose.yml +++ b/gitea-mirror/docker-compose.yml @@ -7,7 +7,7 @@ services: APP_PORT: 4321 web: - image: ghcr.io/raylabshq/gitea-mirror:v3.17.1@sha256:dc5680b13220468bef7845740f7eec0372b8747aac639d9e38d6888e3c4aa6b6 + image: ghcr.io/raylabshq/gitea-mirror:v3.19.0@sha256:6ef8fb2aa21d221cd4d000a46805b70cf3c1ff681b3cea537d01ea31ad5b6461 restart: on-failure user: "1000:1000" volumes: diff --git a/gitea-mirror/umbrel-app.yml b/gitea-mirror/umbrel-app.yml index 271b4f038..4c76b8b43 100644 --- a/gitea-mirror/umbrel-app.yml +++ b/gitea-mirror/umbrel-app.yml @@ -3,7 +3,7 @@ id: gitea-mirror name: Gitea Mirror tagline: Mirror your GitHub repositories to a Gitea instance automatically category: developer -version: "3.17.1" +version: "3.19.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. @@ -42,14 +42,14 @@ defaultUsername: "" defaultPassword: "" dependencies: [] releaseNotes: >- - Gitea Mirror 3.17.1 is a follow-up to the recent 3.17.0 update. If you're updating from a pre-3.17 version 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. + Gitea Mirror 3.19.0 adds Shift-click range selection in the repository table, making it easier to select contiguous groups of repositories. - This release fixes a crash loop that could occur after upgrading to 3.17.0 when the SAML provider migration detected columns that already existed but had not been recorded as migrated. + This update also includes the 3.18.0 fixes for duplicate starred repository mirrors, release activity-log churn, disabled scheduler auto-start behavior, pre-sync backup URL handling, and clearer non-mirror repository sync errors. - Affected instances now repair that migration automatically on startup, preserving SAML provider configuration. Fresh installs, clean upgrades, and already-migrated databases are unchanged. + If you're updating from a pre-3.17 version 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.17.1 + Full release notes can be found at https://github.com/RayLabsHQ/gitea-mirror/releases/tag/v3.19.0 path: ""