Skip to content

chore(deps): update vmactions/freebsd-vm action to v1.5.5 - #87

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vmactions-freebsd-vm-1.x
Open

chore(deps): update vmactions/freebsd-vm action to v1.5.5#87
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vmactions-freebsd-vm-1.x

Conversation

@renovate

@renovate renovate Bot commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
vmactions/freebsd-vm action patch v1.5.3v1.5.5

Release Notes

vmactions/freebsd-vm (vmactions/freebsd-vm)

v1.5.5

Compare Source

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

Compare Source

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


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/vmactions-freebsd-vm-1.x branch from cc5cc61 to aabdff5 Compare August 25, 2026 22:56
@renovate renovate Bot changed the title chore(deps): update vmactions/freebsd-vm action to v1.5.4 chore(deps): update vmactions/freebsd-vm action to v1.5.5 Aug 26, 2026
@renovate
renovate Bot force-pushed the renovate/vmactions-freebsd-vm-1.x branch from aabdff5 to 004554d Compare August 26, 2026 04:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants