build(deps): bump the actions group with 4 updates

[dependabot]

Bumps the actions group with 4 updates: vmactions/solaris-vm, cross-platform-actions/action, github/codeql-action/init and github/codeql-action/analyze.

Updates vmactions/solaris-vm from 1.3.7 to 1.3.9

Release notes

Sourced from vmactions/solaris-vm's releases.

v1.3.9

sync: tar

A new way to share the workspace: the tree is streamed in as a ustar archive over the ssh connection the action already opens, and streamed back the same way when the run finishes. Nothing is installed in the guest and no filesystem support is needed on either side, unlike nfs. solaris-builder v2.0.7 declares it for every release, and it was verified on this guest before the declaration went in: 300 files plus a 1 MB binary blob pushed, a file written inside the VM, the whole tree pulled back and compared by content hash.

rsync remains the default.

Under the hood

solaris-builder v2.0.7 is also the first solaris build to publish releases.json, the machine-readable index this action bakes its configuration from -- which is why the pre-tar method list survived until now.

The runtime moves to anyvm v0.6.5, fifteen releases on from the v0.5.0 that v1.3.8 shipped. Two of its fixes reach every job: a failed folder sync is now fatal instead of a warning that left the guest running without the files it was about to use, and the workspace push no longer carries the runner's own harness directories into the guest.

Full Changelog: vmactions/solaris-vm@v1.3.8...v1.3.9

v1.3.8

The prepare step (installing packages etc.) normally runs on every build. With cache-after-prepare: true, the action shuts the VM down cleanly after prepare has finished, caches the prepared VM image, and boots the VM again before run. Later runs with the same prepare script restore the prepared image, skip prepare entirely, and start directly at run

https://github.com/vmactions/solaris-vm#10-cache-the-vm-image-after-prepare

Full Changelog: vmactions/solaris-vm@v1...v1.3.8

Commits

• 96d8d97 Update vmactions/solaris-vm from base-vm
• f13d129 Generated from base-vm
• f841832 Sync from base-builder
• cb8e2d9 Update vmactions/solaris-vm from base-vm
• 2627719 Generated from base-vm
• 31fc30b Update vmactions/solaris-vm from base-vm
• 8a05dca Generated from base-vm
• a5f8cf8 Update version to v1.3.8
• d45c57a Update vmactions/solaris-vm from base-vm
• a0ddca6 Generated from base-vm
• Additional commits viewable in compare view

Updates cross-platform-actions/action from 1.4.0 to 1.5.0

Release notes

Sourced from cross-platform-actions/action's releases.

Cross Platform Action 1.5.0

Changed

• NetBSD images download around 45% smaller -- 11.0 x86-64 goes from 497 MiB to 268 MiB -- which is most of what a NetBSD job spends on setup (#151)
• Every guest becomes usable sooner, by up to 8 seconds, because the action no longer waits on a readiness probe it sent before the guest was listening
• NetBSD guests are logged into without a credential, so no SSH key is generated and no resources disk is built to carry one. A custom image supplied through image_url still gets both, since it may expect them

Added

• Add support for Haiku R1/beta6 (#165)
• A variant input, selecting a named configuration of a platform. Defaults to default, which boots exactly as before, so no existing workflow changes. See Variants
• The microvm variant for NetBSD on x86-64, which reaches a usable guest in roughly half the time. It is opt-in because it changes the hardware the guest sees: the root disk becomes ld0 rather than sd0, there is no PCI bus to inspect, and uname -v reports a MICROVM kernel. Asking for it where it cannot be booted is an error, not a slow boot
• Log a breakdown of how long each phase of setting up the VM took, together with how long the VM took to become reachable over SSH

Fixed

• 5-level paging (LA57) is no longer exposed to the guests on x86-64 (#158). FreeBSD 13.0 enables 5-level paging whenever the CPU reports it and panics in the trampoline that switches to it, so every job that landed on an Intel runner from Ice Lake onwards failed to boot
• STIBP always-on mode is no longer exposed to the guests on x86-64 (#158). Some of the AMD runners report it without the STIBP and IBRS bits that normally come with it, which made DragonFly BSD write IA32_SPEC_CTRL and take a general protection fault while booting

Security

• The guest's SSH port is only forwarded to the runner's loopback address. It was previously bound to every interface, making the guest reachable from anything that could reach the runner

Changelog

Sourced from cross-platform-actions/action's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

[1.5.0] - 2026-08-28

Changed

• NetBSD images download around 45% smaller -- 11.0 x86-64 goes from 497 MiB to 268 MiB -- which is most of what a NetBSD job spends on setup (#151)
• Every guest becomes usable sooner, by up to 8 seconds, because the action no longer waits on a readiness probe it sent before the guest was listening
• NetBSD guests are logged into without a credential, so no SSH key is generated and no resources disk is built to carry one. A custom image supplied through image_url still gets both, since it may expect them

Added

• Add support for Haiku R1/beta6 (#165)
• A variant input, selecting a named configuration of a platform. Defaults to default, which boots exactly as before, so no existing workflow changes. See Variants
• The microvm variant for NetBSD on x86-64, which reaches a usable guest in roughly half the time. It is opt-in because it changes the hardware the guest sees: the root disk becomes ld0 rather than sd0, there is no PCI bus to inspect, and uname -v reports a MICROVM kernel. Asking for it where it cannot be booted is an error, not a slow boot
• Log a breakdown of how long each phase of setting up the VM took, together with how long the VM took to become reachable over SSH

Fixed

• 5-level paging (LA57) is no longer exposed to the guests on x86-64 (#158). FreeBSD 13.0 enables 5-level paging whenever the CPU reports it and panics in the trampoline that switches to it, so every job that landed on an Intel runner from Ice Lake onwards failed to boot
• STIBP always-on mode is no longer exposed to the guests on x86-64 (#158). Some of the AMD runners report it without the STIBP and IBRS bits that normally come with it, which made DragonFly BSD write IA32_SPEC_CTRL and take a general protection fault while booting

Security

• The guest's SSH port is only forwarded to the runner's loopback address. It was previously bound to every interface, making the guest reachable from anything that could reach the runner

... (truncated)

Commits

• faa0c61 Release 1.5.0
• b77f084 Add support for Haiku R1/beta6
• 0633e66 Don't expose 5-level paging or STIBP always-on mode to the guests
• 1f9f9c4 Merge pull request #162 from cross-platform-actions/claude/netbsd-11-microvm-...
• e631103 Point NetBSD at the release that publishes bundles
• 3a86b11 Tell the microvm guest its TSC is invariant
• 21a2790 Bump the bundled QEMU resources to v2.0.0
• 591c34e Download NetBSD images as a bundle and boot the kernel directly
• 7668283 Add a variant input for picking a configuration of a platform
• 2e33c21 Bound a readiness probe well below the command timeout
• Additional commits viewable in compare view

Updates github/codeql-action/init from 4.37.7 to 4.37.9

Release notes

Sourced from github/codeql-action/init's releases.

v4.37.9

• Update default CodeQL bundle version to 2.26.4. #4106

v4.37.8

No user facing changes.

Changelog

Sourced from github/codeql-action/init's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.37.9 - 26 Aug 2026

• Update default CodeQL bundle version to 2.26.4. #4106

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

• Update default CodeQL bundle version to 2.26.3. #4085

4.37.6 - 04 Aug 2026

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

4.37.3 - 22 Jul 2026

No user facing changes.

4.37.2 - 21 Jul 2026

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

4.37.1 - 16 Jul 2026

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

4.37.0 - 08 Jul 2026

• Update default CodeQL bundle version to 2.26.0. #3995

... (truncated)

Commits

• cdf488f Merge pull request #4107 from github/update-v4.37.9-920ba7cd1
• 7243f38 Update changelog for v4.37.9
• 920ba7c Merge pull request #4106 from github/update-bundle/codeql-bundle-v2.26.4
• ecfa6e1 Add changelog note
• adcdf4a Update default bundle to codeql-bundle-v2.26.4
• 486fec2 Merge pull request #4099 from github/update-supported-enterprise-server-versions
• 134624c Merge pull request #4101 from github/dependabot/npm_and_yarn/npm-minor-457d82...
• ff43db8 Merge pull request #4103 from github/mergeback/v4.37.8-to-main-db488dde
• 4605e03 Rebuild
• 099c869 Update changelog and version after v4.37.8
• Additional commits viewable in compare view

Updates github/codeql-action/analyze from 4.37.7 to 4.37.9

Release notes

Sourced from github/codeql-action/analyze's releases.

v4.37.9

• Update default CodeQL bundle version to 2.26.4. #4106

v4.37.8

No user facing changes.

Changelog

Sourced from github/codeql-action/analyze's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.37.9 - 26 Aug 2026

• Update default CodeQL bundle version to 2.26.4. #4106

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

• Update default CodeQL bundle version to 2.26.3. #4085

4.37.6 - 04 Aug 2026

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

4.37.3 - 22 Jul 2026

No user facing changes.

4.37.2 - 21 Jul 2026

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

4.37.1 - 16 Jul 2026

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

4.37.0 - 08 Jul 2026

• Update default CodeQL bundle version to 2.26.0. #3995

... (truncated)

Commits

• cdf488f Merge pull request #4107 from github/update-v4.37.9-920ba7cd1
• 7243f38 Update changelog for v4.37.9
• 920ba7c Merge pull request #4106 from github/update-bundle/codeql-bundle-v2.26.4
• ecfa6e1 Add changelog note
• adcdf4a Update default bundle to codeql-bundle-v2.26.4
• 486fec2 Merge pull request #4099 from github/update-supported-enterprise-server-versions
• 134624c Merge pull request #4101 from github/dependabot/npm_and_yarn/npm-minor-457d82...
• ff43db8 Merge pull request #4103 from github/mergeback/v4.37.8-to-main-db488dde
• 4605e03 Rebuild
• 099c869 Update changelog and version after v4.37.8
• 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]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml