Silently "pin" before rebasing

General
1

I rebased a few times and just learned that ublue/aurora only “holds” two slots for rollbacks. I thought it pinned each deployment before each rebase, so if I did 5, I could always revert to 2.

Would it be too much of a storage hit if it “silently” pinned images before a rebase command is completed?

Or, make that a prompt.

“Would you like to pin your current image before rebasing?”

Curious if that is feasible feature add worth officially submitting or no?

2

that is how rpm-ostree/bootc works. It keeps the two deployments.

You need to manually pin older ones if you want.

3

There really is no need to keep anything beyond the previous bootable image, because all versions are available online on the container registry anyway. You can always go back, as long as you know the version you need.