Drop MySQL 5.7 support #11154

New Issue

GiteaMirror · 2025-11-02T09:29:11-06:00

GiteaMirror commented

2025-11-02 09:29:11 -06:00

Originally created by @silverwind on GitHub (Jul 3, 2023).

MySQL 5.7 will reach EOL in 4 months. We should:

Drop it from CI matrix and remove relevant Makefile targets
Update docs that MySQL 8.0 or greater is required

Originally created by @silverwind on GitHub (Jul 3, 2023). MySQL 5.7 will reach EOL in [4 months](https://endoflife.date/mysql). We should: - Drop it from CI matrix and remove relevant Makefile targets - Update docs that MySQL 8.0 or greater is required

GiteaMirror added the type/deprecation type/proposal topic/build labels 2025-11-02 09:29:11 -06:00

GiteaMirror closed this issue

2025-11-02 09:29:12 -06:00

GiteaMirror commented

2025-11-02 09:29:13 -06:00

@lunny commented on GitHub (Jul 4, 2023):

We can do it step by step. Firstly prevent new installation to chose mysql 5.7 but that askes Gitea read versions from database.

@lunny commented on GitHub (Jul 4, 2023): We can do it step by step. Firstly prevent new installation to chose mysql 5.7 but that askes Gitea read versions from database.

GiteaMirror commented

2025-11-02 09:29:13 -06:00

@silverwind commented on GitHub (Jul 4, 2023):

I'm primarily looking to remove it from CI. We don't need to deliberatily go out of the way to break it for users unless there are valid reasons to do so.

@silverwind commented on GitHub (Jul 4, 2023): I'm primarily looking to remove it from CI. We don't need to deliberatily go out of the way to break it for users unless there are valid reasons to do so.

GiteaMirror commented

2025-11-02 09:29:13 -06:00

@lunny commented on GitHub (Jul 4, 2023):

Maybe we can have an announcement for that first and maybe 1.22 is a better version to remove mysql5.7 CI and new installation?

@lunny commented on GitHub (Jul 4, 2023): Maybe we can have an announcement for that first and maybe 1.22 is a better version to remove mysql5.7 CI and new installation?

GiteaMirror commented

2025-11-02 09:29:13 -06:00

@silverwind commented on GitHub (Jul 4, 2023):

Sounds ok. We should remove it from CI after 1.22 branch is created. Don't think it needs any big announcement, just update requirements in the docs.

@silverwind commented on GitHub (Jul 4, 2023): Sounds ok. We should remove it from CI after 1.22 branch is created. Don't think it needs any big announcement, just update requirements in the docs.

GiteaMirror commented

2025-11-02 09:29:13 -06:00

@yakob-aleksandrovich commented on GitHub (Sep 27, 2023):

Is there already a roadmap for when support for MySQL 5.7 will be fully dropped? Which branch would that be?
This would help me and various others in planning for an upgrade of our infrastructure.

@yakob-aleksandrovich commented on GitHub (Sep 27, 2023): Is there already a roadmap for when support for MySQL 5.7 will be fully dropped? Which branch would that be? This would help me and various others in planning for an upgrade of our infrastructure.

GiteaMirror commented

2025-11-02 09:29:13 -06:00

@delvh commented on GitHub (Sep 27, 2023):

…

main, since the instant we forked the release/v1.21 branch.

So far, we haven't dropped MySQL 5.7 support.
If it happens, it will probably happen around or after the release of 1.21.0, but not before.

@delvh commented on GitHub (Sep 27, 2023): … `main`, since the instant we forked the `release/v1.21` branch. So far, we haven't dropped MySQL 5.7 support. If it happens, it will probably happen around or after the release of 1.21.0, but not before.

GiteaMirror commented

2025-11-02 09:29:13 -06:00

@silverwind commented on GitHub (Sep 27, 2023):

Will likely happen in 1.22.

@silverwind commented on GitHub (Sep 27, 2023): Will likely happen in 1.22.

GiteaMirror commented

2025-11-02 09:29:13 -06:00

@delvh commented on GitHub (Sep 27, 2023):

Yes, but the question was when exactly is 'in 1.22'.
The range ranges from now to feature freeze in three months…

@delvh commented on GitHub (Sep 27, 2023): Yes, but the question was `when exactly is 'in 1.22'`. The range ranges from now to feature freeze in three months…

GiteaMirror commented

2025-11-02 09:29:14 -06:00

@silverwind commented on GitHub (Sep 27, 2023):

It shouldn't really matter. It will be a sort of soft-deprecation of support anyways, e.g. in theory 5.7 will still work in 1.22, we just don't actively test it anymore, and will start testing 8.0 and likely 8.1 instead.

@silverwind commented on GitHub (Sep 27, 2023): It shouldn't really matter. It will be a sort of soft-deprecation of support anyways, e.g. in theory 5.7 will still work in 1.22, we just don't actively test it anymore, and will start testing 8.0 and likely 8.1 instead.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#11154