build(deps): bump vmactions/netbsd-vm from 1.4.5 to 1.5.2

[dependabot]

Bumps vmactions/netbsd-vm from 1.4.5 to 1.5.2.

Release notes

Sourced from vmactions/netbsd-vm's releases.

v1.5.2

NetBSD 10.2

New release

NetBSD 10.2 on x86_64, aarch64 and sparc64, from image builder 2.2.7 (#39). The default is still 11.0.

• uses: vmactions/netbsd-vm@v1 with: release: "10.2"

The leading-part form follows: release: "10" now picks 10.2, the newest 10.x.

The test matrix runs on ubuntu-26.04 and ubuntu-26.04-arm: 244 of 245 jobs pass, all 24 new 10.2 jobs among them, and the 9p job is skipped as before.

9.x packages

ftp.NetBSD.org dropped every 9.x package directory between 2026-09-17 and 2026-09-25, and with it the 9.0_2026Q1 tree the 9.x images had baked into their PKG_PATH. Image builder 2.2.7 takes that PKG_PATH from ftp.fr.NetBSD.org, else ftp.jaist.ac.jp, and lists every 9.0 quarterly there (9.0_2026Q2 has no fuse-sshfs, 9.0_2026Q1 does).

10.x and 11.x keep their PKG_PATH, except on sparc64, where the build now uses the newest 10.0 quarterly that still carries tree, rsync and fuse-sshfs: upstream deleted 10.0_2024Q3, the only complete sparc64 set.

Pins

BUILDER_VERSION 2.2.6 -> 2.2.7 ANYVM_VERSION 0.7.2 (unchanged)

v1.5.1

NetBSD on ubuntu-26.04 runners, and packages on 9.5 again

The action's test matrix now runs on ubuntu-26.04 and ubuntu-26.04-arm: 220 of 221 jobs pass, and the 9p job is skipped as before.

What failed on 26.04

With v1.5.0 on a 26.04 runner:

... (truncated)

Commits

• c8a0d7d Update vmactions/netbsd-vm from base-vm
• 054725d Generated from base-vm
• 5b23cf3 Bump versions from upstream releases
• 7ed8c60 Update version to v1.5.1
• 876c34f Update vmactions/netbsd-vm from base-vm
• f7357ac Generated from base-vm
• d9f80b5 fix 9.5
• 35f290d Update vmactions/netbsd-vm from base-vm
• 59429fe Generated from base-vm
• 55d652b Bump versions from upstream releases
• 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)