Align schema of image-info.json with Bazzite

[ledif]

There are a few discrepancies between the fields of /usr/share/ublue-os/image-info.json in Aurora and Bazzite. We should consider aligning these fields.

On my Aurora machine:

{
  "image-name": "aurora-dx",
  "image-flavor": "main",
  "image-vendor": "ublue-os",
  "image-ref": "ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx",
  "image-tag":"stable",
  "base-image-name": "kinoite",
  "fedora-version": "41"
}

On my Bazzite machine:

{
  "image-name": "bazzite-nvidia-open",
  "image-flavor": "nvidia-open",
  "image-vendor": "ublue-os",
  "image-ref": "ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open",
  "image-tag": "41",
  "image-branch": "stable",
  "base-image-name": "kinoite",
  "fedora-version": "41",
  "version": "41.20250106",
  "version-pretty": "Stable (F41.20250106)"
}

Key differences:

• image-tag refers to the update stream in Aurora, but refers to the upstream Fedora version in Bazzite
• image-branch is missing in Aurora but refers to the update stream in Bazzite
• version and version-pretty are absent in Aurora

[inffy]

Seems we are using the same format as Bluefin

{
"image-name": "bluefin",
"image-flavor": "main",
"image-vendor": "ublue-os",
"image-ref": "ostree-image-signed:docker://ghcr.io/ublue-os/bluefin",
"image-tag":"latest",
"base-image-name": "silverblue",
"fedora-version": "41"
}

[RealVishy]

Do we know what it looks like on base kinoite?

[inffy]

I'll check Kinoite in a few but I would guess its pretty much the same as ours

[inffy]

Tried to look for the file in my Kinoite VM but atleast cannot find it under /usr/share/

i think kinoite might not use this in anything. But I also don’t know how this file is used in Aurora/Bluefin/Bazzite so dont know which one we should follow.

[ledif]

As far as I'm aware, this file is a Universal Blue specific file that is only used by our internal tooling. It's not currently a problem because we can control the schema of it, but it does make it more difficult if we want to share processes (e.g., scripts) between Bazzite and Aurora.

I only ran into this because I was implementing #93 and I had to change how this file is interpreted in the code based on whether I was testing it on Aurora vs Bazzite.

So bottom line, this isn't a high priority but more of a nice to have.