chore(deps): update dependency lima-vm/lima to v2 #1002
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.2.2->v2.0.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
lima-vm/lima (lima-vm/lima)
v2.0.1Compare Source
Changes
Binary release artifacts:
level=fatal msg="template \"_images/<IMAGE>.yaml\" not found"(#4313, thanks to @vvoland)Misc:
SIGINTinstead ofSIGKILL(#4310, thanks to @norio-nomura)Full changes: https://github.com/lima-vm/lima/milestone/64?closed=1
Usage
The binaries were built automatically on GitHub Actions.
The build log is available for 90 days: https://github.com/lima-vm/lima/actions/runs/19137304035
The sha256sum of the SHA256SUMS file itself is
25ad222fa1cf91a85ef7be67664f2ba65228a5d82a39be1adbbe842096854e24.Release manager: @AkihiroSuda
v2.0.0Compare Source
This is the second major release of Lima, featuring the support for pluggable VM drivers, GPU acceleration, and MCP.
This release also commemorates the promotion of the project from CNCF Sandbox to Incubating 🎉.
Highlights
This will help implementing third-party plugins without modifying the code base of Lima.
Thanks to GSoC 2025 contributor @unsuman .
limactl (start|restart) --progressflag to show the progress of provisioning (#3846, #3915, thanks to @olamilekan000 @norio-nomura)limactl shell --preserve-envflag to propagate env vars from the host to VM (#3830, thanks to @olamilekan000)Other notable changes
/tmp/limais no longer mounted by default (#3951)template://defaultis now recommended to be written astemplate:default. The old form is still supported.Details
VM driver infrastructure:
krunkit:
VZ:
AF_VSOCK(#3979, thanks to @norio-nomura)QEMU:
MCP:
limactlCLI:limactl (start|restart) --progressflag to show the progress of provisioning (#3846, #3915, thanks to @olamilekan000 @norio-nomura)limactl (create|start|edit) --port-forwardflag for static port forwarding (#3699, thanks to @Horiodino).Usually not needed, but useful for instances created with
--plain.limactl (create|start|edit) --ssh-portflag (#3791)limactl (create|start|edit) --mount-onlyflag (#3947).Similar to
--mount, but overrides the existing mounts. Useful for mounting$(pwd).--setmultiple times inlimactl (create|start|edit)(#4197, thanks to @AndiDog)limactl shell --preserve-envflag to propagate env vars from the host to VM (#3830, thanks to @olamilekan000).See also
LIMA_SHELLENV_ALLOWandLIMA_SHELLENV_BLOCK.template://defaultis now recommended to be written astemplate:default. The old form is still supported.limactl copy --backend=rsyncflag as an alternative toscpbackend (#3143, thanks to @olamilekan000)limactl list--yqandlimactl info --yqflags (#3998, thanks to @jandubois)limactl rename OLD NEW(#4207)--yesand introducelimactl (clone|rename|edit|shell) --startinstead (#4108, #4285, thanks to @Horiodino @nlordell)YAML:
cpuTypetovmOpts.qemu(#3500, thanks to @unsuman)yqprovision mode (#3892, thanks to @norio-nomura)Relative paths were never intended to be supported,
but they were accidentally allowed due to a regression in v1.1.0.
The CLI command
limactl (create|start|edit) --mount DIRstill supports relative paths.Default template:
/tmp/limamount (#3951)Network:
Port forwarding:
sudo nerdctl run -p ...(#4107).sudo nerdctl run -p ...now requires nerdctl v2.1.6 or later.guestIPMustBeZerototruewhenguestIPis0.0.0.0(#4221, thanks to @jandubois)Build system:
Kconfigandconfig.mk, in favor of Makefile variables (#3732)Templates:
alpine,alpine-iso: update to Alpine 3.22 (#4184, #4190, thanks to @jandubois)debian: update to Debian 13 (#4029, thanks to @unsuman)docker,docker-rootful: Enable containerd image store (#3941, thanks to @norio-nomura)fedora: update to Fedora 43 (#4255)opensuse: update to openSUSE Leap 16 (#4203)oraclelinux: update to Oracle Linux 10 (#4236, thanks to @valdela1)ubuntu,default: update Ubuntu to 25.10 (#4202)k0s: New template (#3728, thanks to @plandem)experimental/ubuntu-next: update to Ubuntu 26.04 pre-release (#4311)Project:
Full changes: https://github.com/lima-vm/lima/milestone/59?closed=1
Thanks to @AndiDog @Horiodino @afbjorklund @alexandear @ashwat287 @balajiv113 @bonifaido @dharsanb @gnawhleinad @iamleot @jandubois @kachick @muchzill4 @ningmingxiao @nlordell @norio-nomura @olamilekan000 @plandem @stek29 @unsuman @valdela1 @vax-r @vishalanarase @zyfy29
EOL of v1.2
Lima v1.2 will continue to receive security updates and critical bug fixes until 2026-02-06 (3 months from now).
See also https://lima-vm.io/docs/releases/.
Usage
The binaries were built automatically on GitHub Actions.
The build log is available for 90 days: https://github.com/lima-vm/lima/actions/runs/19130682878
The sha256sum of the SHA256SUMS file itself is
112f1ef1d9850e29b4be425ca71e8b6ac686f593ff741164885b51fbd6919ca6.Release manager: @AkihiroSuda
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.