chore(deps): update vmactions/freebsd-vm action to v1.5.7

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
vmactions/freebsd-vm	action	patch	v1.5.6 → v1.5.7

---

Release Notes

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

v1.5.7

Compare 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.

• uses: vmactions/freebsd-vm@​v1
  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:

• New input: token. It defaults to github.token and is handed to the
  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.
• anyvm 0.7.1: the release-URL probe retries transient failures and
  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

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • "after 1am and before 8am"
• Automerge
  • At any time (no schedule defined)

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

♻ Rebasing: Never, 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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud