[renovate]

This PR contains the following updates:

Package	Type	Update	Change
vmactions/freebsd-vm	action	minor	v1.5.9 → v1.6.0

---

Release Notes

vmactions/freebsd-vm

v1.6.0

Compare Source

FreeBSD 15.x: UFS root by default, ZFS as 15.0-zfs / 15.1-zfs

The 15.0 and 15.1 images now have a UFS root, the same as 10.4 - 14.5.
Before this release they had a ZFS root. A ZFS root is available as two
new releases, 15.0-zfs and 15.1-zfs, on x86_64, aarch64 and riscv64.
Requested in anyvm-org/freebsd-builder#1

Usage

  - uses: vmactions/freebsd-vm@v1
    with:
      release: "15.1-zfs"

• Without release:, the default is still 15.1, now on UFS.
• There is no -zfs image for powerpc64: the powerpc64 images are
  installed from the ISO with the default UFS layout.
• The -zfs releases have the same sync methods as the plain release
  on the same arch.

Pins

BUILDER_VERSION 2.2.8 -> 2.2.9
ANYVM_VERSION 0.7.2 -> 0.7.7

https://github.com/anyvm-org/freebsd-builder/releases/tag/v2.2.9
https://github.com/anyvm-org/anyvm/releases/tag/v0.7.7

Full Changelog: vmactions/freebsd-vm@v1.5.9...v1.6.0

---

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.

[rami3l]

Looks like the CI failure is some sort of GitHub instability...

View changes since this review

[rami3l]

Actually no, it looks like cargo as shipped in Rust v1.100.0 has broken our test harness. I'll look into it.

[rustbot]

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[rami3l]

Actually no, it looks like cargo as shipped in Rust v1.100.0 has broken our test harness. I'll look into it.

Addressed in #5211.