github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-17 13:42:23 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

official docker image: tag "1" downgraded from 1.11.1 to 1.10.5 #5019

New Issue
Closed
opened 2025-11-02 06:11:07 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 06:11:07 -06:00
Owner
Copy Link

Originally created by @dujiulun on GitHub (Mar 7, 2020).

  • Gitea version (or commit ref): 1.10.5 / 1.11.1
  • Git version: Not relevant
  • Operating system: Docker
  • 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 use the official docker image (gitea/gitea)[https://hub.docker.com/r/gitea/gitea] with tag "1" because I want to stay on the 1.x branch. Previously it was mapped to 1.11.1. Today when I restart and re-pull the image, my gitea version is downgraded to 1.10.5.

IMHO semantic tags like "1" or "1.11" should always point to the latest version in that branch and not go backwards.

Screenshots

gitea-docker

Tag "1" has the same digest as 1.10.5.

Originally created by @dujiulun on GitHub (Mar 7, 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.10.5 / 1.11.1 - Git version: Not relevant - Operating system: Docker - Database (use `[x]`): - [ ] PostgreSQL - [ ] 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 use the official docker image (gitea/gitea)[https://hub.docker.com/r/gitea/gitea] with tag "1" because I want to stay on the 1.x branch. Previously it was mapped to 1.11.1. Today when I restart and re-pull the image, my gitea version is downgraded to 1.10.5. IMHO semantic tags like "1" or "1.11" should always point to the latest version in that branch and not go backwards. ## Screenshots ![gitea-docker](https://user-images.githubusercontent.com/5555270/76143759-07893100-60b5-11ea-9390-0773b50da457.png) Tag "1" has the same digest as 1.10.5. <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the topic/build label 2025-11-02 06:11:07 -06:00
GiteaMirror commented 2025-11-02 06:11:08 -06:00
Author
Owner
Copy Link

@0x5c commented on GitHub (Mar 8, 2020):

I got the same problem on my end. The migration code wasn't happy about that

@0x5c commented on GitHub (Mar 8, 2020): I got the same problem on my end. The migration code wasn't happy about that
GiteaMirror commented 2025-11-02 06:11:08 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Mar 8, 2020):

I've re-tagged the docker images. This is now fixed.

@techknowlogick commented on GitHub (Mar 8, 2020): I've re-tagged the docker images. This is now fixed.
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#5019
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?