You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Require MySQL 8.0, PostgreSQL 12, MSSQL 2012 (#27337)
- MySQL 5.7 support and testing is dropped
- MySQL tests now execute against 8.1, up from 5.7 and 8.0
- PostgreSQL 10 and 11 support ist dropped
- PostgreSQL tests now execute against 16, up from 15
- MSSQL 2008 support is dropped
- MSSQL tests now run against locked 2022 version
Fixes: #25657
Ref: https://endoflife.date/mysql
Ref: https://endoflife.date/postgresql
Ref: https://endoflife.date/mssqlserver
## ⚠️ BREAKING ⚠️
Support for MySQL 5.7, PostgreSQL 10 and 11, and MSSQL 2008 is dropped.
You are encouraged to upgrade to supported versions.
---------
Co-authored-by: techknowlogick <[email protected]>
Copy file name to clipboardExpand all lines: docs/content/installation/database-preparation.en-us.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,9 @@ menu:
17
17
18
18
# Database Preparation
19
19
20
-
You need a database to use Gitea. Gitea supports PostgreSQL (>=10), MySQL (>=5.7), MariaDB, SQLite, and MSSQL (>=2008R2 SP3). This page will guide into preparing database. Only PostgreSQL and MySQL will be covered here since those database engines are widely-used in production. If you plan to use SQLite, you can ignore this chapter.
20
+
You need a database to use Gitea. Gitea supports PostgreSQL (>= 12), MySQL (>= 8.0), MariaDB, SQLite, and MSSQL (>= 2012 SP4). This page will guide into preparing database. Only PostgreSQL and MySQL will be covered here since those database engines are widely-used in production. If you plan to use SQLite, you can ignore this chapter.
21
+
22
+
If you use an unsupported database version, please [get in touch](/help/support) with us for information on our Extended Support Contracts. We can provide testing and support for older databases and integrate those fixes into the Gitea codebase.
21
23
22
24
Database instance can be on same machine as Gitea (local database setup), or on different machine (remote database).
Copy file name to clipboardExpand all lines: tests/e2e/README.md
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,6 @@ They can be run with make commands for the appropriate backends, namely:
7
7
make test-sqlite
8
8
make test-pgsql
9
9
make test-mysql
10
-
make test-mysql8
11
10
make test-mssql
12
11
```
13
12
@@ -76,7 +75,7 @@ For SQLite:
76
75
make test-e2e-sqlite#example
77
76
```
78
77
79
-
For other databases(replace `mssql` to `mysql`, `mysql8` or `pgsql`):
78
+
For other databases(replace `mssql` to `mysql` or `pgsql`):
80
79
81
80
```
82
81
TEST_MSSQL_HOST=localhost:1433 TEST_MSSQL_DBNAME=test TEST_MSSQL_USERNAME=sa TEST_MSSQL_PASSWORD=MwantsaSecurePassword1 make test-e2e-mssql#example
@@ -90,4 +89,4 @@ Although the main goal of e2e is assertion testing, we have added a framework fo
90
89
91
90
VISUAL_TEST=1 will create screenshots in tests/e2e/test-snapshots. The test will fail the first time this is enabled (until we get visual test image persistence figured out), because it will be testing against an empty screenshot folder.
92
91
93
-
ACCEPT_VISUAL=1 will overwrite the snapshot images with new images.
92
+
ACCEPT_VISUAL=1 will overwrite the snapshot images with new images.
0 commit comments