adam/gitea-mirror
1
0 Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-10-30 22:21:58 +01:00
Code Issues 4 Packages Projects Releases Wiki Activity

Pulled latest docker image, still version 3.36.0, not 3.36.1 #168

New Issue
Closed
opened 2026-10-05 01:45:35 +02:00 by adam · 1 comment
adam commented 2026-10-05 01:45:35 +02:00
Owner
Copy link
Copy source

I've pulled the latest docker image.
Verified the digest
ghcr.io/raylabshq/gitea-mirror latest sha256:f772cc84ad1b4b05cd93cacae2fe9636fba1baad6c8fdf607e8a79cf747352a9

But it still shows v3.36.0.
In logging: Setting application version: 3.36.0
In web UI:

Image
I've pulled the latest docker image. Verified the digest `ghcr.io/raylabshq/gitea-mirror latest sha256:f772cc84ad1b4b05cd93cacae2fe9636fba1baad6c8fdf607e8a79cf747352a9` But it still shows v3.36.0. In logging: ```Setting application version: 3.36.0``` In web UI: <img width="250" height="52" alt="Image" src="https://github.com/user-attachments/assets/4c81c89b-650d-401d-be58-67f5ed35793f" /> <!-- github-sync-id:5432224021 -->
adam closed this issue 2026-10-05 01:45:35 +02:00
adam commented 2026-10-05 01:45:36 +02:00
Author
Owner
Copy link
Copy source

Thanks for the precise report, the digest made this quick to trace.

The squash merge of #424 and the version bump for 3.36.1 were pushed four seconds apart. Both commits triggered the image build and both builds pushed latest. The 3.36.1 build pushed at 00:19:05, the 3.36.0 build pushed at 00:19:24 and won. sha256:f772cc84... is that 3.36.0 build. The weekly scheduled rebuild on 2026-09-13 repushed latest from main, so a pull today gives you 3.36.1 (sha256:9de8d704...).

Fixed in #431, released in v3.36.2: the workflow runs one build per ref at a time, latest is only pushed by a stable release tag build, and main builds push edge and the short commit sha instead. That removes the race for good.

Thanks for the precise report, the digest made this quick to trace. The squash merge of #424 and the version bump for 3.36.1 were pushed four seconds apart. Both commits triggered the image build and both builds pushed `latest`. The 3.36.1 build pushed at 00:19:05, the 3.36.0 build pushed at 00:19:24 and won. `sha256:f772cc84...` is that 3.36.0 build. The weekly scheduled rebuild on 2026-09-13 repushed `latest` from main, so a pull today gives you 3.36.1 (`sha256:9de8d704...`). Fixed in #431, released in v3.36.2: the workflow runs one build per ref at a time, `latest` is only pushed by a stable release tag build, and main builds push `edge` and the short commit sha instead. That removes the race for good. <!-- github-comment-id:5690954820 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/gitea-mirror#168