RayLabsHQ/gitea-mirror v3.51.5 on GitHub

Fixed

A Postgres DATABASE_URL started the app over with an empty database (#505, refs #502 and #358). gitea-mirror only supports SQLite. Until v3.25.0 it did not read DATABASE_URL at all, so a setup with a postgresql:// URL there kept its data in data/gitea-mirror.db. From v3.25.0 the URL was read as a file path, which opened a new, empty database outside the data volume, and the push engine put its clones next to it. Any scheme other than sqlite:// and file: is now ignored with a warning, and the app uses data/gitea-mirror.db again.

If your setup looked wiped after an upgrade and you have a postgresql:// or other non-SQLite DATABASE_URL, this release opens your earlier data again. Remove the variable, or set it to file:data/gitea-mirror.db, to drop the warning.
Anything you set up again after hitting this lived in that other file, outside the data volume, and is not carried over.

No other action needed. As always, back up your Gitea before upgrading.

Full Changelog: v3.51.4...v3.51.5