2 Commits

Author	SHA1	Message	Date
Earl Warren	4b000cb435	[DB] forgejo migration v2: create the forgejo_sem_ver table ... (cherry picked from commit 86b26436af) (cherry picked from commit 479cba59ac) (cherry picked from commit 4765f9a889) (cherry picked from commit af771410bf) (cherry picked from commit d1ea9305d8) (cherry picked from commit f77e1bb7ab) (cherry picked from commit 0b95f8fe89) (cherry picked from commit 4f8fb2390a) (cherry picked from commit 8ea0e22ff6) (cherry picked from commit 43ac19ac59) (cherry picked from commit 0d2f63df4f) (cherry picked from commit d02a8036fd) (cherry picked from commit 1fe4c7db94) (cherry picked from commit d641cdeaf0) (cherry picked from commit 10e8a4f8b8) (cherry picked from commit 8097bc40b3) (cherry picked from commit ee5cb37d7e) (cherry picked from commit 26d93b8e49) (cherry picked from commit bc73195e59) (cherry picked from commit a763fa5de2)	2024-01-01 13:50:27 +01:00
Gusted	e5c446e3dc	[DB] Forgejo database migrations ... - Implements https://codeberg.org/forgejo/discussions/issues/32#issuecomment-918737 - Allows to add Forgejo-specific migrations that don't interfere with Gitea's migration logic. Please do note that we cannot liberally add migrations for Gitea tables, as they might do their own migrations in a future version on that table, and that could undo our migrations. Luckily, we don't have a scenario where that's needed and thus not taken into account. Co-authored-by: Gusted <postmaster@gusted.xyz> Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/795 (cherry picked from commit 8ee32978c0) (cherry picked from commit c240b34f59) (cherry picked from commit 03936c6492) (cherry picked from commit a20ed852f8) (cherry picked from commit 1dfa82676f) (cherry picked from commit c39ae0bf8a) (cherry picked from commit cfaff08996) (cherry picked from commit 94a458835a) (cherry picked from commit 61a3cf77df) (cherry picked from commit abb350fde8) (cherry picked from commit 5194829d6b) (cherry picked from commit 89239a60f2) (cherry picked from commit 683cfd86ef) (cherry picked from commit f4546cfed9) (cherry picked from commit 86614d5826) (cherry picked from commit e4b9c32187) (cherry picked from commit 8c253719af) (cherry picked from commit 857365d6c1) (cherry picked from commit a488b3952f) (cherry picked from commit 98313c4910) (cherry picked from commit 430d95e824) (cherry picked from commit 08bf9d918f) (cherry picked from commit f8a170e2d0) (cherry picked from commit d20e325378) (cherry picked from commit 6c0aa7dd4f) (cherry picked from commit 46c08c26c7) (cherry picked from commit 9ee22153c4) [DB] Ensure forgejo migration up to date (squash) - Hook Forgejo's `EnsureUpToDate` to Gitea's `EnsureUpToDate`, such that the Forgejo migrations are also being checked to be up to date. - I'm not sure how I missed this and if this has caused any problems, but due to the lack of any open issue about it it seems to not be a big problem. (cherry picked from commit 6c65b6dcf6) (cherry picked from commit 6d45c37d84) [DB] Add test for TestEnsureUpToDate (squash) - Add a test for the behavior of `EnsureUpToDate`, to ensure it will error when needed and succeed when the forgejo version is up to date. - Add forgejo_migrations package to GO_TEST_PACKAGES, to avoid running it with `test-unit` and instead test it with `test-*-migration`. (cherry picked from commit b172a50691) (cherry picked from commit d8af308820) (cherry picked from commit e69e64a32c) (cherry picked from commit 4e8363fad4) (cherry picked from commit fc9ecd6c53)	2024-01-01 13:50:27 +01:00