Skip to content

chore(deps): update vmactions/solaris-vm action to v1.4.2 - #105

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vmactions-solaris-vm-1.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vmactions-solaris-vm-1.x

Conversation

@renovate

@renovate renovate Bot commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
vmactions/solaris-vm action patch v1.4.1 → v1.4.2

Release Notes

vmactions/solaris-vm

v1.4.2

Compare Source

Solaris: non-root users can write the nfs-synced folder

The runtime moves to anyvm 0.7.4, whose nfs fix is the reason for this
release: https://github.com/anyvm-org/anyvm/releases/tag/v0.7.4
On ubuntu-26.04 runners 23 of 25 test jobs pass; the 9p and sshfs jobs
are skipped as before.

Fixed: non-root users could not write the nfs share

#​70: with sync: nfs, a build run as an ordinary
user created in the guest failed with "Permission denied", while the
same workflow worked on FreeBSD. The nfs export mapped only guest root
to the runner user; any other guest account kept its own uid and met
the runner-owned workspace as "other". FreeBSD worked by coincidence:
its first pw useradd hands out uid 1001, the GitHub runner's own uid.
Solaris useradd hands out 1000.

anyvm 0.7.4 now maps every guest uid to the runner user: the kernel nfs
export of a Linux runner gets all_squash, and on other hosts the
user-space nfsd 0.1.1 runs with -all_squash. Files any guest user
creates are owned by the runner user on the host, as files from guest
root already were. Nothing to change in your workflow.

The test matrix now checks this on every release: a guest user with
uid 4321 creates, appends to and renames a file in the share, and the
runner checks its content and that the runner user owns it.

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

Optional, empty by default. A non-empty value is appended to the
cache-after-prepare key, so changing it rebuilds the prepared image.
Use it when prepare runs a script from your repository, which the key
does not cover (vmactions/freebsd-vm#167), for example:

cache-after-prepare-key-suffix: deps-${{ hashFiles('ci/deps.sh') }}

Existing prepared-image caches stay valid when the input is not set.

Pins

BUILDER_VERSION 2.0.8 (unchanged)
ANYVM_VERSION 0.7.2 -> 0.7.4


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR becomes conflicted, 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.

@renovate
renovate Bot force-pushed the renovate/vmactions-solaris-vm-1.x branch from b0c65bc to decec0b Compare October 27, 2026 00:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants