xyny

https://www.mankier.com/5/containers-policy.json#Policy_Requirements-sigstoreSigned

> which in my opinion adds so little security as to be not worth the effort. It is also required for secure boot to work AFAIK.

Sure, ok, that might be a misconception that I've gotten from somewhere. I could not find much information either way online, and I'm too lazy to test it out lol....

As in, do the same thing as `rpm-ostree rebase` and `bootc switch`?

And with VanillaOS, it would be updating the `abroot.json`. With #65, such a command would have to be a new command, though, with nothing to do with building images.

Sounds good!

I think the `br-` prefix makes sense here, but with the other stuff I believe I discussed this with @gmpinder earlier. Maybe [here](https://github.com/blue-build/cli/issues/7), maybe some parts where somewhere else. Anyway,...

Not sure what you mean by that question. My earlier comment explains my stance on the topic.

Either a new page in the docs, but I think it'd belong to a reference page for the cli, which has yet to be made. Such a page should document...

Can we guarantee that the `cosign.pub` will exist at a specific place in the repo, or is there a label we could add that would point directly to it?