Earl Warren 8bfc117458 [DB] run all Forgejo migrations in integration tests ... The tests at tests/integration/migration-test/migration_test.go will not run any Forgejo migration when using the gitea-*.sql.gz files because they do not contain a ForgejoVersion row which is interpreted as a new Forgejo installation for which there is no need for migration. Create a situation by which the ForgejoVersion table exists and has a version of 0 in tests/integration/migration-test/forgejo-v1.19.0.*.sql.gz thus ensuring all Forgejo migrations are run. The forgejo*.sql.gz files do not have any Gitea related records, which will be interpreted by the Gitea migrations as a new installation that does not need any migration. As a consequence the migration tests run when using forgejo-v1.19.0.*.sql.gz are exclusively about Forgejo migrations. (cherry picked from commit ec8003859c) (cherry picked from commit 697570ff39) (cherry picked from commit f041aec172) (cherry picked from commit 60463e3bab) (cherry picked from commit b2fc2a7c13) (cherry picked from commit fb2759b6af) (cherry picked from commit 37cfc3b227) (cherry picked from commit 832607500a) (cherry picked from commit 143d4007b1) (cherry picked from commit a17e803fbf) (cherry picked from commit 5c1cc8d9f6)		2023-10-16 15:50:10 +02:00
..
forgejo-v1.19.0.mysql.sql.gz	[DB] run all Forgejo migrations in integration tests	2023-10-16 15:50:10 +02:00
forgejo-v1.19.0.postgres.sql.gz	[DB] run all Forgejo migrations in integration tests	2023-10-16 15:50:10 +02:00
forgejo-v1.19.0.sqlite3.sql.gz	[DB] run all Forgejo migrations in integration tests	2023-10-16 15:50:10 +02:00
gitea-v1.6.4.mssql.sql.gz
gitea-v1.6.4.mysql.sql.gz
gitea-v1.6.4.postgres.sql.gz
gitea-v1.6.4.sqlite3.sql.gz
gitea-v1.7.0.mssql.sql.gz
gitea-v1.7.0.mysql.sql.gz
gitea-v1.7.0.postgres.sql.gz
gitea-v1.7.0.sqlite3.sql.gz
migration_test.go	[DB] run all Forgejo migrations in integration tests	2023-10-16 15:50:10 +02:00