milestone 1.21.12 release #14498

New Issue

GiteaMirror · 2025-11-02T11:14:34-06:00

GiteaMirror commented

2025-11-02 11:14:34 -06:00

Originally created by @mbarinc on GitHub (May 15, 2025).

Feature Description

I have this issue 30684 on my Gitea 1.21.11 on-premise. I can't upgrade Gitea to 1.22 or later because I need to upgrade before DB.
When will the 1.21.12 milestone be released?

Screenshots

No response

Originally created by @mbarinc on GitHub (May 15, 2025). ### Feature Description I have this issue [30684](https://github.com/go-gitea/gitea/issues/30684) on my Gitea 1.21.11 on-premise. I can't upgrade Gitea to 1.22 or later because I need to upgrade before DB. When will the [1.21.12](https://github.com/go-gitea/gitea/milestone/163) milestone be released? ### Screenshots _No response_

GiteaMirror added the issue/needs-feedback label 2025-11-02 11:14:34 -06:00

GiteaMirror closed this issue

2025-11-02 11:14:34 -06:00

GiteaMirror commented

2025-11-02 11:14:35 -06:00

@lunny commented on GitHub (May 15, 2025):

You can use the branch version https://dl.gitea.com/gitea/1.21/ directly even if 1.21.12 wasn't released.

@lunny commented on GitHub (May 15, 2025): You can use the branch version https://dl.gitea.com/gitea/1.21/ directly even if 1.21.12 wasn't released.

GiteaMirror commented

2025-11-02 11:14:35 -06:00

@wxiaoguang commented on GitHub (May 16, 2025):

I can't upgrade Gitea to 1.22 or later because I need to upgrade before DB.

You don't need to.

https://docs.gitea.com/installation/upgrade-from-gitea

@wxiaoguang commented on GitHub (May 16, 2025): > I can't upgrade Gitea to 1.22 or later because I need to upgrade before DB. You don't need to. https://docs.gitea.com/installation/upgrade-from-gitea

GiteaMirror commented

2025-11-02 11:14:35 -06:00

@mbarinc commented on GitHub (May 19, 2025):

Thanks for the reply.
I will use the nightly to bring in my Gitea environment the commits released after 1.21.11 (and therefore the fix I'm interested in).
However, I ask you if the official release of 1.21.12 is planned, because in the Production environment I would like to keep only official versions and not nightly.

@mbarinc commented on GitHub (May 19, 2025): Thanks for the reply. I will use the nightly to bring in my Gitea environment the commits released after 1.21.11 (and therefore the fix I'm interested in). However, I ask you if the official release of 1.21.12 is planned, because in the Production environment I would like to keep only official versions and not nightly.

GiteaMirror commented

2025-11-02 11:14:35 -06:00

@wxiaoguang commented on GitHub (May 19, 2025):

However, I ask you if the official release of 1.21.12 is planned, because in the Production environment I would like to keep only official versions and not nightly.

There won't be new 1.21.x release. After a new version becomes a stable release, usually the old releases won't get more supports. For example: when 1.22.0 gets released, then there won't be new 1.21.x releases.

Now the stable release is 1.23.x, and it will be 1.24.x soon.

@wxiaoguang commented on GitHub (May 19, 2025): > However, I ask you if the official release of 1.21.12 is planned, because in the Production environment I would like to keep only official versions and not nightly. There won't be new 1.21.x release. After a new version becomes a stable release, usually the old releases won't get more supports. For example: when 1.22.0 gets released, then there won't be new 1.21.x releases. Now the stable release is 1.23.x, and it will be 1.24.x soon.

GiteaMirror referenced this issue

2025-11-02 11:16:24 -06:00

Suddenly need authToken to access packages in Gitea registry #14564

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#14498