Repository navigation
Update vmactions/freebsd-vm action to v1.5.9 - #120
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/vmactions-freebsd-vm-1.x
branch
2 times, most recently
from
September 4, 2026 14:51
1031cd4 to
ff15463
Compare
renovate
Bot
force-pushed
the
renovate/vmactions-freebsd-vm-1.x
branch
from
September 9, 2026 21:49
ff15463 to
6fa00b1
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
renovate
Bot
force-pushed
the
renovate/vmactions-freebsd-vm-1.x
branch
from
September 15, 2026 00:52
6fa00b1 to
4300978
Compare
renovate
Bot
force-pushed
the
renovate/vmactions-freebsd-vm-1.x
branch
2 times, most recently
from
September 19, 2026 01:14
28d068e to
ea3d6df
Compare
renovate
Bot
force-pushed
the
renovate/vmactions-freebsd-vm-1.x
branch
from
September 26, 2026 07:56
ea3d6df to
402fa04
Compare
renovate
Bot
force-pushed
the
renovate/vmactions-freebsd-vm-1.x
branch
from
October 1, 2026 21:12
402fa04 to
8a363d4
Compare
renovate
Bot
force-pushed
the
renovate/vmactions-freebsd-vm-1.x
branch
from
October 3, 2026 09:37
8a363d4 to
d4d0c79
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.5.4→v1.5.9Release Notes
vmactions/freebsd-vm (vmactions/freebsd-vm)
v1.5.9Compare Source
Optional key suffix for the cache-after-prepare cache
New input cache-after-prepare-key-suffix: an optional value that is
appended as-is to the cache key of the image cached after prepare.
Changing it discards that cache and runs prepare again, without
editing prepare itself. Requested in
#167
Usage
key stays the same as in v1.5.8, so existing caches stay valid.
the suffix is only added at the end.
so check out first. It returns an empty string when no file
matches, and the key then no longer follows the file.
Pins
BUILDER_VERSION 2.2.8 (unchanged)
ANYVM_VERSION 0.7.2 (unchanged)
v1.5.8Compare Source
FreeBSD on ubuntu-26.04 runners
The action's test matrix, 10.4, 11.4 and 13.2 - 15.1 across x86_64,
aarch64, riscv64 and powerpc64, now runs on ubuntu-26.04 and
ubuntu-26.04-arm: 313 of 314 jobs pass, and the 9p job is skipped as
before. 12.4, which the matrix leaves out, passes anyvm's own FreeBSD CI
on the same runners.
What failed on 26.04
With v1.5.7 on a 26.04 runner:
Every aarch64 job, on both runner types, timed out in the firmware.
The serial log holds only the banner of 26.04's edk2 2025.11, which
hangs under -cpu max:
tianocore/edk2#11962
Every riscv64 job stopped at
Error: QEMU binary 'qemu-system-riscv64' not found (searched PATH
and common install locations).
Since Ubuntu 25.10 the riscv64 emulator ships in a separate
qemu-system-riscv package, no longer in qemu-system-misc.
With the emulator installed, 13.2, 13.3, 13.5, 14.0, 14.1, 14.2 and
14.3 riscv64 still hung after the last PCI device attached, before
"Timecounters tick", on QEMU 10.2.1.
x86_64 and powerpc64 were not affected.
Fixes
and, for 2025.08 and later, boots with Ubuntu 24.04's edk2 2024.02
build instead, downloaded once and checked against a pinned sha256.
QEMU 10.1 and later; 14.4, 14.5 and 15.x keep Sstc.
for riscv64 on Ubuntu releases newer than 24.04.
Each fix engages only on a newer firmware, QEMU or Ubuntu release than
24.04 ships, so jobs on ubuntu-24.04 run as before. Details:
https://github.com/anyvm-org/anyvm/releases/tag/v0.7.2
Pins
BUILDER_VERSION 2.2.8 (unchanged)
ANYVM_VERSION 0.7.1 -> 0.7.2
v1.5.7Compare Source
FreeBSD 10.4 and 11.4, and a fix for "Unsupported OS: freebsd"
New releases
FreeBSD 10.4 and 11.4 on x86_64, from image builder 2.2.8. The action
now offers 15 releases; the default is still 15.1.
with:
release: "10.4"
The leading-part form works too: release: "10" and release: "11" pick
the newest matching release, so the action now ships 10, 11, 12, 13, 14
and 15.
pkg.FreeBSD.org dropped its FreeBSD 10, 11 and 12 repositories long
ago, so these images take their packages from the preserved SGGS
mirror (https://mirror.sg.gs/freebsd-pkg/), which keeps FreeBSD's
original repository signatures; pkg verifies them against the
fingerprint shipped in the base system. Two things the VM runtime had
to learn to run them: 10.x and 11.x boot via SeaBIOS, since their
images have no EFI system partition, and 10.4 runs on QEMU's qemu64
CPU model, because FreeBSD 10's signal delivery panics when -cpu host
exposes modern XSAVE features.
12.4 x86_64 gains rsync and sshfs
The same mirror reaches 12.4 x86_64: the image now ships rsync and
fusefs-sshfs, so all five sync methods work there instead of nfs, scp
and tar only. 12.4 aarch64 stays base-only; no aarch64 packages exist
for FreeBSD 12.
Fixed: a lost network probe no longer fails as "Unsupported OS"
#163: a job with release: '14.0' failed after three minutes with
Error: Unsupported OS: freebsd. Builder repository
anyvm-org/freebsd-builder not found.
although the image exists. A single failed probe of the release
download URL sent the run down the GitHub REST API. The action never
passed a token, so that request was unauthenticated and shared the
60/hour per-IP limit with every other job on the runner IP; the 403
was retried for three minutes and then reported as an unsupported OS.
Two changes close this:
VM runtime, so the release lookup is authenticated (1000 requests
per hour per repository instead of 60 shared). Nothing to change
in your workflow; set it only if you want a different token.
only a 404 means the image is absent; a rate-limited 403 or a 429
stops the retry loop at once and reports the reset time; "the API
could not be asked" and "this repository does not exist" are
distinct outcomes, so a connectivity failure is reported as one;
and the Authorization header no longer follows a cross-host
redirect.
Pins
BUILDER_VERSION 2.2.7 -> 2.2.8
ANYVM_VERSION 0.6.9 -> 0.7.1
v1.5.6Compare Source
FreeBSD 14.5, and riscv64 can install packages
New releases
FreeBSD 14.5 on x86_64, aarch64, riscv64 and powerpc64. The action now
offers 13 releases; the default is still 15.1.
riscv64 gains rsync and sshfs
pkg.FreeBSD.org publishes no riscv64 packages at all, so the riscv64
images used to ship without rsync or fusefs-sshfs and only nfs, scp and
tar worked there. Image builder 2.2.7 configures the 15.0 and 15.1
riscv64 images for anyvm-org/freebsd-pkg-repo, a signed build of the
ports tree for FreeBSD:15:riscv64, so those two releases now support
all five sync methods:
sync: rsync (the default)
sync: sshfs
sync: nfs
sync: scp
sync: tar
pkg install also works inside the VM on those images. 13.x and 14.x
riscv64 are unchanged and stay on nfs, scp and tar.
Pins
BUILDER_VERSION 2.2.6 -> 2.2.7
ANYVM_VERSION 0.6.5 -> 0.6.9
Fixes from base-vm
for AlmaLinux/Rocky ppc64le does not apply here.
v1.5.5Compare 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
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.