Repository navigation
What triggers image builds and pushes to quay.io for Keycloak releases? #38717
Replies: 1 comment
|
I don't have an answer but also wondering what happens for the Quay images and the Keycloak tags, ( information correct as of today being April 10, 2025 ). What I don't understand and think this where where the OP question comes from; To elaborate the question with information:- When we look here on Github for the tags: github keycloak
Looking over at Quay for the images available and their tags, with filter for the 26.0 series: Quay.io keycloak tags
When we see the earlier releases. 26.0.6 and 26.0.7, their Github tags and their Quay build tags align by naming and also by date. Something has happened, at February 20, and so created 26.0.8-1 with 26.0 and 26.0.8 tags updated to point to it. That's okay. The earlier releases are present between Github tag and Quay builds, so why aren't these most recent pair for 26.0.9 and 26.0.10 available on Quay? |
Uh oh!
There was an error while loading. Please reload this page.
Hello Keycloak Community,
I’m trying to understand what exactly triggers a Keycloak image build and subsequent push to quay.io
I noticed there’s a formal release for 26.0.8, but tags exist for 26.0.9 and 26.0.10 containing some backported fixes. However, these later tags have no associated GitHub release and haven't resulted in new images being pushed to Quay.
I'm hoping I haven't missed some blaringly obvious documented process here. If someone could clarify:
What specifically triggers image builds and pushes?
What determines when a GitHub release is officially created versus just tagging the repository?
Thanks in advance for your help.
All reactions