Incorrect version tag for release versions #946

New Issue

GiteaMirror · 2025-11-02T03:42:48-06:00

GiteaMirror commented

2025-11-02 03:42:48 -06:00

Originally created by @tgurr on GitHub (Aug 7, 2017).

Currently the version tag is hardcoded in main.go and doesn't get updated when you do proper releases.

// Version holds the current Gitea version
var Version = "1.1.0+dev"

For git head of the current development branch a 1.1.0+dev seems fine but for a proper release like e.g. 1.1.3 the version tag should get updated accordingly.

Originally created by @tgurr on GitHub (Aug 7, 2017). Currently the version tag is hardcoded in main.go and doesn't get updated when you do proper releases. ``` // Version holds the current Gitea version var Version = "1.1.0+dev" ``` For git head of the current development branch a 1.1.0+dev seems fine but for a proper release like e.g. 1.1.3 the version tag should get updated accordingly.

GiteaMirror added the issue/not-a-bug label 2025-11-02 03:42:48 -06:00

GiteaMirror closed this issue

2025-11-02 03:42:48 -06:00

GiteaMirror commented

2025-11-02 03:42:49 -06:00

@lunny commented on GitHub (Aug 7, 2017):

You should use make to do that. You can test https://dl.gitea.io/gitea/1.1.3, the tag is correct.

@lunny commented on GitHub (Aug 7, 2017): You should use `make` to do that. You can test https://dl.gitea.io/gitea/1.1.3, the tag is correct.

GiteaMirror referenced this issue

2025-11-02 11:51:55 -06:00

[PR #946] [MERGED] fix: 500 error on /explore/repos page #15668

Sign in to join this conversation.