Release 1.16.9 miss update of docker tags

[nemunaire]

Description

Docker tags gitea/gitea:1 and gitea/gitea:1.16 (+*-rootless) still point to the 1.16.8 release. They don't have been updated to point to the 1.16.9 image.

Intermediate tags, arch specific (1.16-linux-amd64, ...) are presents, so it seems it's the docker manifest step for :1.16 that's missing. Regarding :1 tag, I don't see any arch specific tag neither.

Gitea Version

1.16.9

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Git Version

No response

Operating System

No response

How are you running Gitea?

Through Docker

Database

No response

[zeripath]

Tag 1 is not being updated by 1.16.9

1.16 should have been updated.

[zeripath]

what's interesting is that 1.16-linux-amd64 and 1.16-linux-arm64-rootless did get updated.

[zeripath]

OK I've manually pushed 1.16 separately.

[nbr23]

Thanks @zeripath! Looks like only the amd64 architecture image was tagged with 1.16 btw, not the arm64.
1.16.9 has both architectures.

[SuNNjek]

Is there a reason that tag "1" is not being updated to 1.16.9? It has previously pointed to the latest patch and currently points to 1.16.8. Is there an alternative tag that can be pulled to get the latest stable release instead?

[zeripath]

I had been told that 1 was pointing to 1.17-rc1 but it appears that that is not the case...

[zeripath]

I've pushed 1.16.9 as 1.16 and 1
and I've push 1.16.9-rootless as 1.16-rootless and 1-rootless

I hope that this is everything correct now.

[zeripath]

ugh it looks like the arm64 ones also need to be pushed... ffs.

[lunny]

I've pushed 1.16.9 as 1.16 and 1 and I've push 1.16.9-rootless as 1.16-rootless and 1-rootless

I hope that this is everything correct now.

You should not push to 1.

[zeripath]

It was fine. 1 was pointing at 1.16.8 not 1.17-rc1.

[zeripath]

The issue is that I cannot push an arm64 tag as those need manifests.

We could just release 1.16.10 once I have restored auto_tagging.