Why is 'quay.io/fedora/fedora-silverblue' outdated?

Hi!
I have recently switched my systems to use OCI container images,
but it came to my attention that I am still running F39 with no updates pending.
turns out the “latest” tag in quay.io/fedora/fedora-silverblue is still pointing to F39,
and even after rebasing to: ‘ostree-remote-registry:fedora:quay.io/fedora/fedora-silverblue:40’,
my systems are still on version: 40.20240419.n.0 which is not the latest compose.
should I revert back to the production ostree branch? or will updates be pushed to ‘quay.io/fedora/fedora-silverblue’?

So, after reading a lot of threads, I found this:
https://pagure.io/releng/blob/main/f/scripts/sync-latest-container-base-image.sh

This is the release of Fedora that is currently stable, it will define if we

need to move the fedora:latest tag

current_stable=“39”

Define what is rawhide so we know to push that tag

current_rawhide=“41”

When this is updated, i can continue following the “latest” tag, right?

Opened a pull request: PR#12079: container latest tag now points to Fedora 40 - releng - Pagure.io

See Quay.io/fedora/fedora-silverblue:39 not updated - #5 by siosm

2 Likes