github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Docker tag gitea/gitea:1 is not monotonic #5603

New Issue
Closed
opened 2025-11-02 06:30:32 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 06:30:32 -06:00
Owner
Copy Link

Originally created by @hweidner on GitHub (Jun 21, 2020).

  • Gitea version (or commit ref): 1.12.0 / 1.11.8
  • Git version: 2.20.1
  • Operating system: Debian GNU/Linux 10
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

I ran Gitea from the Docker Hub image gitea/gitea:1. Until now, this was Gitea 1.12.0. After a docker pull today, it downgraded to Gitea 1.11.8. This is unexpected, I always thought that the tag does not downgrade.

I'd suggest making the tag gitea/gitea:1 monotonic. I.e. even when newer versions of 1.11.x come out, gitea/gitea:1 stays 1.12.0 until 1.12.1 gets released.

Originally created by @hweidner on GitHub (Jun 21, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.12.0 / 1.11.8 - Git version: 2.20.1 - Operating system: Debian GNU/Linux 10 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description I ran Gitea from the Docker Hub image gitea/gitea:1. Until now, this was Gitea 1.12.0. After a docker pull today, it downgraded to Gitea 1.11.8. This is unexpected, I always thought that the tag does not downgrade. I'd suggest making the tag gitea/gitea:1 monotonic. I.e. even when newer versions of 1.11.x come out, gitea/gitea:1 stays 1.12.0 until 1.12.1 gets released. <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the topic/build label 2025-11-02 06:30:32 -06:00
GiteaMirror commented 2025-11-02 06:30:33 -06:00
Author
Owner
Copy Link

@pabloyoyoista commented on GitHub (Jun 21, 2020):

This could possibly be fixed by #11897 or is at least related

@pabloyoyoista commented on GitHub (Jun 21, 2020): This could possibly be fixed by #11897 or is at least related
GiteaMirror commented 2025-11-02 06:30:33 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Jun 21, 2020):

It should be now 1.12.1. It was just pointing to 1.11.8 in between while drone does build version. When releasing versions in multiple releases branches like this time v1.11.8 and v1.12.1 it could point to wrong version for some time as Gitea release process takes more than hour to finish. It should not happen often as we rarely do minor versions to two major version branches.

@lafriks commented on GitHub (Jun 21, 2020): It should be now 1.12.1. It was just pointing to 1.11.8 in between while drone does build version. When releasing versions in multiple releases branches like this time v1.11.8 and v1.12.1 it could point to wrong version for some time as Gitea release process takes more than hour to finish. It should not happen often as we rarely do minor versions to two major version branches.
GiteaMirror commented 2025-11-02 06:30:33 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Jun 21, 2020):

Closing this as fixed as now it points correctly but in long term should be fixed in #11897

@lafriks commented on GitHub (Jun 21, 2020): Closing this as fixed as now it points correctly but in long term should be fixed in #11897
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/build
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5603
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?