NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #3012 by repository stars
Last release 13 days ago
24 Sep 2026
Ships unpredictably
gaps range from 8 days to 12 months
Some releases are documented
notes for 14 of 55 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
119 releases · first in 2020
One column per quarter.
Nothing published for this version
cloudinit.apt_mirror config option to point apt in Debian and Ubuntu VMs at a local mirror. Requires cloud-init 18.4 or newer in the guest image.
cloudinit.apt_mirror config option to point apt in Debian and Ubuntu VMs at
a local mirror. Requires cloud-init 18.4 or newer in the guest image.Shared disks and raw extra disks are created as sparse volumes instead of being fully allocated up front.
Disk I/O errors are reported to the guest instead of pausing the whole VM, so a full host disk no longer looks like a silent stall.
vm run --id reclaims a DHCP reservation left behind by an interrupted
vm rm instead of failing with "preset ID already used".image build no longer panics when interrupted during the commit phase.image build --push-to flag to push to a registry reference while keeping a separate local image name.
image build --push-to flag to push to a registry reference while keeping a
separate local image name.image build --push rejects destinations without a registry early instead
of failing later with an authentication error.disk ls and disk rm no longer fail when a VM is removed concurrently.
disk ls and disk rm no longer fail when a VM is removed concurrently.virter disk command group (create, ls, rm) to manage shared disks that can be attached to multiple VMs at once.
virter disk command group (create, ls, rm) to manage shared disks
that can be attached to multiple VMs at once.vm run --shared-disk flag to attach a shared disk. Shared disks survive
vm rm and cannot be removed while attached.--config-set key=value flag on all commands to override config file and
environment variable settings.Nothing published for this version
provisioning: add user field to container step
provisioning: add user field to container step
Add a `user` field on the container provisioning step that overrides
the user the container's command runs as. Plumbs through to
containerapi.WithUser, equivalent to `docker run --user`. Accepts a
numeric uid, uid:gid, or a name from the image's /etc/passwd; an empty
value keeps the image default.
Useful with execution-environment images (e.g. anything built by
ansible-builder) that default to a non-root uid: virter binds the SSH
key under /root/.ssh, which such users cannot read, so setting
`user = "0"` works as a workaround.
user field on the container provisioning step to override the user the
container command runs as.⚠️ v1.0.0 introduces a few breaking changes against v0.x.
⚠️ v1.0.0 introduces a few breaking changes against v0.x.
See the migration guide to learn more.
See doc/migration-1.0.md for the full 0.x to 1.0 migration guide.
vm list --sort flag to sort by name, id, network, or state. Output
is sorted by name by default.vm rm no longer logs every deleted layer; image commands log a single
summary line instead.--bootcapacity and --bootcap flags. Use --boot-capacity.auth.user_public_key accepts a single string again instead of splitting it
on whitespace.⚠️ Breaking Changes in this release
--pull-policy flag removed: The deprecated --pull-policy flag was removed from vm run and image build. Use --vm-pull-policy instead.
--bootcapacity / --bootcap deprecated: Renamed to --boot-capacity for consistency. The old flags still work but print a deprecation warning and will be removed in a future release.
Unknown keys in provisioning files are now errors: Previously, unknown TOML keys in provisioning files produced a warning. Now they cause a hard error. This catches typos (e.g. destination instead of dest) but will break any provisioning files that relied on extra/misspelled keys being silently ignored.
Provisioning filesystem access restricted to working directory: rsync.source paths and container.copy.dest paths in provisioning steps are now validated to be within the current working directory. Provisioning files that reference paths outside the working directory (e.g. absolute paths like /etc/... or paths that escape via ../) will now fail.
build(deps): bump github.com/spf13/viper from 1.20.0 to 1.20.1
build(deps): bump github.com/spf13/viper from 1.20.0 to 1.20.1
Bumps [github.com/spf13/viper](https://github.com/spf13/viper) from 1.20.0 to 1.20.1.
- [Release notes](https://github.com/spf13/viper/releases)
- [Commits](spf13/viper@v1.20.0...v1.20.1)
Nothing published for this version
Nothing published for this version
check for nil desc.Metadata before attempting to unmarshall, avoiding…
check for nil desc.Metadata before attempting to unmarshall, avoiding…
… a segfault for non-virter VMs (#33)
Nothing published for this version
Nothing published for this version
If 'truncate' fails for /etc/machine-id during 'commit', attempt with…
If 'truncate' fails for /etc/machine-id during 'commit', attempt with…
… 'sudo' before giving up
If 'truncate' fails for /etc/machine-id, attempt with 'sudo' before giving up (#29). Also, fix a spelling error in the help messages.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Release v0.27.0 Compare # Choose a tag to compare
Release v0.27.0
Compare
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
virter: pass-through exit code from provisioning
virter: pass-through exit code from provisioning
When a provisioning step fails, it may be helpful to the caller of
virter to know the exit code of the script.
So, if an SSH or container provisioning step fails with an exit code,
pass it through to the CLI, exiting from the virter process with the
same exit code.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →