Aaand it’s here.

After a ujust update, rpm-update status reports

State: idle
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:9ef3035588c6760e96c5064a1920db35c012c6c8e7d20ac6c1c31a04ed682e0b
                  Version: 45.20261104 (2026-11-04T00:33:01Z)
            SecAdvisories: 4 unknown severity, 6 low, 15 moderate, 9 important
                     Diff: 2626 upgraded, 14 downgraded, 148 removed, 78 added

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:ee82a885dbb77cd4604a5ffa8278a0eef0bc84d16850045c7b9d847729da9949
                  Version: 44.20261026 (2026-10-26T20:06:36Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:d1617c7098adb290bdf37e1b6661fa68467fced5771336425cfa985db4ded7e6
                  Version: 44.20261023 (2026-10-23T16:31:37Z)

So the last 44 is 1 (0 base) and I do a sudo ostree admin pin 1 before rebooting. It’s not that I distrust Bazzite or Fedora before them, it’s that they really can’t test against all the weird and wonderful hardware out there, and you might only pick up a subtle flaw a week or two in. A couple of weeks from now I’ll do a sudo ostree admin pin -u 2 to remove it (there’ll be 3 deployments until then)