v1.0.2

sync: tar

A second way to move the workspace. Android ships no rsync, no sshfs and
no NFS client, so scp was the only option until now; sync: tar streams
the tree as a ustar archive over the same connection and is the faster
of the two on a large tree. Nothing is installed in the guest. Verified
on this guest before the declaration went in: 300 files plus a 1 MB
binary blob pushed, a file written inside the VM, the whole tree pulled
back and compared by content hash.

scp remains the default.

Under the hood

The image builder moves to blissos-builder v2.0.3 and the runtime to
anyvm v0.6.5, fifteen releases on from the v0.5.0 that v1.0.1 shipped.
The builder now mirrors its dropbear source tarball at a pinned version
-- an upstream download hiccup used to produce an image missing its ssh
server instead of a red build -- and publishes releases.json, the
machine-readable index this action bakes its configuration from.

Two runtime fixes reach every job: a failed folder sync is now fatal
instead of a warning that left the guest running without the files it
was about to use, and the workspace push no longer carries the runner's
own harness directories into the guest.

Full Changelog: v1.0.1...v1.0.2

v1.0.1

The prepare step (installing packages etc.) normally runs on every build. With cache-after-prepare: true, the action shuts the VM down cleanly after prepare has finished, caches the prepared VM image, and boots the VM again before run. Later runs with the same prepare script restore the prepared image, skip prepare entirely, and start directly at run

https://github.com/vmactions/blissos-vm#10-cache-the-vm-image-after-prepare

Full Changelog: v1...v1.0.1

v1.0.0

init

Full Changelog: https://github.com/vmactions/blissos-vm/commits/v1.0.0