Please issue docker images before releasing security patches #8741

New Issue

GiteaMirror · 2025-11-02T08:16:09-06:00

GiteaMirror commented

2025-11-02 08:16:09 -06:00

Originally created by @erikh on GitHub (Mar 24, 2022).

Feature Description

Currently, there have been multiple instances where gitea releases have been cut and I have been notified of their release, with full security details, and no docker image to pull. The latest example is today, but I suspect this is just a timing issue of CI or what-have-you. I'm not really upset about this other than it really makes it hard to track releases in a security-minded manner for services that are exposed to the internet.

Thank you for considering my griping; I don't have anything else to add here.

Screenshots

No response

Originally created by @erikh on GitHub (Mar 24, 2022). ### Feature Description Currently, there have been multiple instances where gitea releases have been cut and I have been notified of their release, with full security details, and no docker image to pull. The latest example is today, but I suspect this is just a timing issue of CI or what-have-you. I'm not really upset about this other than it really makes it hard to track releases in a security-minded manner for services that are exposed to the internet. Thank you for considering my griping; I don't have anything else to add here. ### Screenshots _No response_

GiteaMirror added the type/feature type/proposal labels 2025-11-02 08:16:09 -06:00

GiteaMirror closed this issue

2025-11-02 08:16:09 -06:00

GiteaMirror commented

2025-11-02 08:16:10 -06:00

@techknowlogick commented on GitHub (Mar 24, 2022):

This was previously the case where the release email went out after CI, however github changed their behaviour where they send an email on tag, instead of release. As long as we use GitHub we are beholden to their changes. However the migration to gitea.com is very much in progress.

@techknowlogick commented on GitHub (Mar 24, 2022): This was previously the case where the release email went out after CI, however github changed their behaviour where they send an email on tag, instead of release. As long as we use GitHub we are beholden to their changes. However the migration to gitea.com is very much in progress.

GiteaMirror commented

2025-11-02 08:16:10 -06:00

@erikh commented on GitHub (Mar 24, 2022):

gotcha; thanks for the response!

@erikh commented on GitHub (Mar 24, 2022): gotcha; thanks for the response!

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#8741