Question about upgrading Gitea with minor versions #820

New Issue

GiteaMirror · 2025-11-02T03:37:46-06:00

GiteaMirror commented

2025-11-02 03:37:46 -06:00

Originally created by @Avalancs on GitHub (Jun 18, 2017).

I noticed that versions get backport fixes, and I would like to upgrade from 1.1.1 version (from 1 month before) inside the company to 1.1 which contains some fixes to issues I raised. But I did not find anything on minor version upgrades, even though I tried searching the Gitea docs, and "migration", "upgrade" keywords on GitHub.

My main concern is changes in the database schema, such as in the commit 506c98df5b . Is there any general guide/advice on upgrading? Of course I can export database schema from 1.1.1 and 1.1 then compare, but if there is a better way I would like to know.

We are very satisfied with Gitea in general, thanks for this awesome software!

Originally created by @Avalancs on GitHub (Jun 18, 2017). I noticed that versions get backport fixes, and I would like to upgrade from 1.1.1 version (from 1 month before) inside the company to 1.1 which contains some fixes to issues I raised. But I did not find anything on minor version upgrades, even though I tried searching the Gitea docs, and "migration", "upgrade" keywords on GitHub. My main concern is changes in the database schema, such as in the commit 506c98df5bd7d795491906645d8f9befbf91e91a . Is there any general guide/advice on upgrading? Of course I can export database schema from 1.1.1 and 1.1 then compare, but if there is a better way I would like to know. We are very satisfied with Gitea in general, thanks for this awesome software!

GiteaMirror added the type/question label 2025-11-02 03:37:46 -06:00

GiteaMirror closed this issue

2025-11-02 03:37:46 -06:00

GiteaMirror commented

2025-11-02 03:37:47 -06:00

@cez81 commented on GitHub (Jun 18, 2017):

1.1 is a not a release, it's the development branch for 1.1.x track. If you mean you want to upgrade to 1.1.2 from 1.1.1, that's fine. Migration scripts deals with db changes. To be safe, do a backup first, then just replace the binary.

@cez81 commented on GitHub (Jun 18, 2017): 1.1 is a not a release, it's the development branch for 1.1.x track. If you mean you want to upgrade to 1.1.2 from 1.1.1, that's fine. Migration scripts deals with db changes. To be safe, do a backup first, then just replace the binary.

GiteaMirror commented

2025-11-02 03:37:47 -06:00

@Avalancs commented on GitHub (Jun 19, 2017):

Ahh okay, thank you!

@Avalancs commented on GitHub (Jun 19, 2017): Ahh okay, thank you!

GiteaMirror referenced this issue

2025-11-02 11:50:10 -06:00

[PR #820] [MERGED] fix: ignore email notifications if user is not active. #15592

Sign in to join this conversation.