chore(deps): update vmactions/solaris-vm action to v1.4.1 - #99
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.4.0→v1.4.1Release Notes
vmactions/solaris-vm (vmactions/solaris-vm)
v1.4.1Compare Source
Solaris on ubuntu-26.04 runners
The action is now tested on ubuntu-26.04 runners: its test matrix has
moved there from 24.04, and 30 of 32 jobs pass; the 9p and sshfs jobs
are skipped as before. The runtime moves to anyvm 0.7.2, the release
that brings Ubuntu 26.04 host support:
https://github.com/anyvm-org/anyvm/releases/tag/v0.7.2
Fixed: a lost network probe no longer fails as "Unsupported OS"
vmactions/freebsd-vm#163: a job 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. This action took
the same path. Two changes close it:
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.
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.0.8 (unchanged)
ANYVM_VERSION 0.6.9 -> 0.7.2
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.