Change docker tag logic #16421
Merged
Change docker tag logic #16421
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
1 of 3 tasks
|
This requires an update in |
Co-authored-by: Kyle D. <[email protected]>
|
@kdumontnu docs have been updated :) |
|
|
zeripath
merged commit e180456
into
go-gitea:main
2 checks passed
2 checks passed
approvals/lgtm
this commit looks good
|
Wait, do the manifest/docker plugins have the logic to not tag |
|
No it does not have |
|
That was quick in the end |
|
@kdumontnu it is a problem already existing previously and we always have to re-build a latest. |
2 of 6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
This PR changes the image tagged as
:lateston docker hub to represent the:latestreleased version of Gitea.:latestwill now be mapped to latest tag on the 1.15 branch.:devwill represent the latest build from themainbranch.Replace: #15889
Fixes #15622
thanks to @pat-s for the initial work on this PR :)
Previously the
:latestdocker tag would map to the latest build frommain. Users who wish to use the absolute latest version of Gitea should migrate to use:devand we would ask that at least some users do consider using the:devtag if possible.