v0.22 planning about lima HOT 5 CLOSED

I would prefer #2295 to be reverted if 0.22 has to be released before the regression is fixed.

Should I do an Alpine-Lima release and bump for 0.22 as well?

from lima.

Should I do an Alpine-Lima release and bump for 0.22 as well?

There is an Alpine 19.1 available, maybe want to rebuild with that

from lima.

There is an Alpine 19.1 available, maybe want to rebuild with that

I think this is just an issue with naming the build. IIUC Alpine ISO builds are not "repeatable", they just pull the latest packages from the 3.19 repo at the time of the build.

You can see that our current image self-identifies as 3.19.1 internally:

$ l shell alpine cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.19.1
PRETTY_NAME="Alpine Linux v3.19"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"
BUILD_ID="v0.2.38"
VARIANT_ID="std"

But it may very well include packages that are updated beyond the versions from the 3.19.1 tag of the aports repo.

So maybe we should change the image name to just mention 3.19 instead of 3.19.0, but that shouldn't be a Lima 0.22 blocker.

from lima.

Will make a release after merging:

• #2320

from lima.

https://github.com/lima-vm/lima/releases/tag/v0.22.0

from lima.