[dependabot]

Bumps the actions group with 2 updates: vmactions/tribblix-vm and vmactions/ghostbsd-vm.

Updates vmactions/tribblix-vm from 1.0.6 to 1.0.7

Release notes

Sourced from vmactions/tribblix-vm's releases.

v1.0.7

Tribblix 0m41.1, now the default release

Tribblix 0m41.1, the point update to the 0m41 milestone, is available as release: "0m41.1" and is now the default when release is omitted (it was 0m41). 0m39, 0m40 and 0m41 are unchanged and still available. Tribblix stays x86_64 only, so the default move drops no architecture.

The test matrix runs on ubuntu-26.04 runners across 0m39, 0m40, 0m41 and 0m41.1: 23 of 25 jobs pass; the 9p and sshfs jobs are skipped as before.

New input: cache-after-prepare-key-suffix

vmactions/freebsd-vm#167: with cache-after-prepare: true, the prepared VM image was keyed only on the prepare script and the sync method, so there was no way to throw it away by hand. The new optional input is appended to that cache key; change its value and the next run starts from the base image and runs prepare again. Empty, the default, keeps the key and your existing caches as they are. Only an exact key match restores a prepared image, so a run without a suffix never picks up an entry saved with one.

Fixed: non-root guest users can write the nfs share

With sync: nfs, only guest root was mapped to the runner user. Any other guest account kept its own uid and could write the synced folder only if that uid happened to be the runner's (1001). anyvm 0.7.4 squashes every guest uid to the runner user, so a build that runs as an unprivileged account (useradd test; su test -c make) can now write the share, and the files it creates are owned by the runner user on the host. The nfs test jobs now check this on every release: https://github.com/anyvm-org/anyvm/releases/tag/v0.7.4

Pins

BUILDER_VERSION 2.0.7 -> 2.0.8 ANYVM_VERSION 0.7.2 -> 0.7.5

Commits

• 3420c87 Update vmactions/tribblix-vm from base-vm
• 9373160 Generated from base-vm
• fbf3f91 0m41.1
• 4b09f64 Update version to v1.0.6
• 884e75b Update vmactions/tribblix-vm from base-vm
• 853584e Generated from base-vm
• 75fcd9a Bump versions from upstream releases
• 725a5b6 Update vmactions/tribblix-vm from base-vm
• 3c8d71d Generated from base-vm
• c0be0fb Update vmactions/tribblix-vm from base-vm
• Additional commits viewable in compare view

Updates vmactions/ghostbsd-vm from 1.0.4 to 1.0.5

Release notes

Sourced from vmactions/ghostbsd-vm's releases.

v1.0.5

GhostBSD 26.2, now the default release

GhostBSD 26.2 (26.2-R15.1p6, based on FreeBSD 15.1) is available in two editions, release: "26.2" (MATE) and release: "26.2-xfce", and 26.2 is now the default when release is omitted (it was 26.1). Upstream ships no Gershwin ISO for 26.2, so there is no 26.2-gershwin; use release: "26.1-gershwin" for that desktop. 26.1, 26.1-xfce and 26.1-gershwin are unchanged. GhostBSD stays x86_64 only, so the default move drops no architecture.

The test matrix runs on ubuntu-26.04 runners across all five releases: 31 of 32 jobs pass; the 9p job is skipped as before.

New input: cache-after-prepare-key-suffix

vmactions/freebsd-vm#167: with cache-after-prepare: true, the prepared VM image was keyed only on the prepare script and the sync method, so there was no way to throw it away by hand. The new optional input is appended to that cache key; change its value and the next run starts from the base image and runs prepare again. Empty, the default, keeps the key and your existing caches as they are. Only an exact key match restores a prepared image, so a run without a suffix never picks up an entry saved with one.

Fixed: non-root guest users can write the nfs share

With sync: nfs, only guest root was mapped to the runner user. Any other guest account kept its own uid and could write the synced folder only if that uid happened to be the runner's (1001). anyvm 0.7.4 squashes every guest uid to the runner user, so a build that runs as an unprivileged account (pw useradd test; su test -c make) can now write the share, and the files it creates are owned by the runner user on the host. The nfs test jobs now check this on every release: https://github.com/anyvm-org/anyvm/releases/tag/v0.7.4

Pins

BUILDER_VERSION 2.0.8 -> 2.0.9 ANYVM_VERSION 0.7.2 -> 0.7.5

Commits

• d223228 Update vmactions/ghostbsd-vm from base-vm
• f0894ef Generated from base-vm
• bc0fd9d 26.2
• 2e08395 Update version to v1.0.4
• d9735d4 Update vmactions/ghostbsd-vm from base-vm
• 401af86 Generated from base-vm
• 7795f2d Bump versions from upstream releases
• eef5668 Update vmactions/ghostbsd-vm from base-vm
• c61773d Generated from base-vm
• e8591d1 Update vmactions/ghostbsd-vm 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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.