build(deps): bump vmactions/freebsd-vm from 1.5.3 to 1.5.5 in the actions group

[dependabot]

Bumps the actions group with 1 update: vmactions/freebsd-vm.

Updates vmactions/freebsd-vm from 1.5.3 to 1.5.5

Release notes

Sourced from vmactions/freebsd-vm's releases.

v1.5.5

The runtime moves to anyvm v0.6.5 (from v0.6.4), keeping the whole fleet on one version. This action's surface is unchanged -- same images, same sync methods, same defaults. The bump carries one runtime change of note: on hosts whose nested AMD virtualization corrupts AVX512 XSAVE state, the CPU-feature mask now drops the whole AVX512 family instead of only avx512f.

Full Changelog: vmactions/freebsd-vm@v1.5.4...v1.5.5

v1.5.4

sync: tar

A fourth way to share the workspace, available on every architecture including riscv64 and powerpc64, where rsync and sshfs do not exist:

The workspace is streamed in as a ustar archive over the ssh connection the action already opens, and streamed back the same way when the run finishes. Nothing is installed in the guest and no filesystem support is needed on either side, unlike sshfs and nfs. Verified before shipping: 300 files plus a 1 MB binary blob pushed into a 15.1 guest, a file written inside it, the whole tree pulled back and compared by content hash.

rsync remains the default. Reach for tar when the guest lacks rsync, or when a mount-based method is more machinery than the job needs.

Under the hood

The image builder moves to freebsd-builder v2.2.6 and the runtime to anyvm v0.6.4, nine releases on from what v1.5.3 shipped. Most of that is other guests, but two fixes reach every action:

A failed folder sync used to be a warning. The run continued with the guest missing the files it was about to use, which surfaced much later as a confusing error or a job that sat until its timeout. It is now fatal, and says so.

The workspace push no longer carries the runner's own harness directories into the guest.

Also

The shell note no longer mentions usesh, which has not been needed for some time.

Full Changelog: vmactions/freebsd-vm@v1.5.3...v1.5.4

Commits

• f0552d3 Update vmactions/freebsd-vm from base-vm
• 5595fc6 Generated from base-vm
• 0206b2a Sync from base-builder
• 2ed1747 Update vmactions/freebsd-vm from base-vm
• be1c6e8 Generated from base-vm
• bddcfce Update vmactions/freebsd-vm from base-vm
• 139a2cb Generated from base-vm
• 0a1a391 Update version to v1.5.4
• 759dd0c Update vmactions/freebsd-vm from base-vm
• b5370dd Generated from base-vm
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions