Robert Sturla

Awesome! Specifying the --all flag does do it! Thank you (I thought the --all flag essentially merged two multi-image manifests together, but I guess that's not the case).

It would probably be worth opening an issue in https://github.com/containers/container-libs to support this, since bootc inherits Skopeo for verification, which inherits container-libs. Though I'm not too sure how this would...

We can create a base Renovate configuration in `ublue-os/.github//renovate-presets/default.json5`, as you suggested before. This base configuration can contain the "config:best-practices" preset, plus the logic to exclude pinning on the Containerfiles....

We're currently using hhd-dev/rechunk to split our images into smaller layers, making updates easier to download. rpm-ostree has recently added built-in support for rechunking. A general rule-of-thumb for bluefin-lts has...

We can probably do this with Renovate. Manage the version number in an arbitrary file, allow Renovate to auto update changes to that file and builds will kick off after...

We also have an option to switch up our approach. We can only pin the BASE images to a specific digest, and allow GHA to build the image using that...

Needs some extra configuration. Will hold this PR

Personally, I like the sound of option 2 - and we can provide a single Just script that iterates over the Quadlets, allowing the user to select the one they...

Didn't we gain something from this kernel for Framework or Surface machines? I seem to remember the introduction of fsync meant we could turn off some vendor-specific builds, but can't...

I agree for the end-user facing images like Bluefin and Aurura, though I think it's overkill for main. A key thing to consider would be to not increase maintenance workload...