Update GitHub Actions to current major versions - #736
Merged
Conversation
Bumps every third-party action in the IKVM workflow to its latest release, except the GitVersion actions which are intentionally left on v3/5.x. Also pins jlumbroso/free-disk-space from the floating `main` branch to v1.3.1; the tag and `main` currently point at identical trees, so this is a no-op for behavior while removing an unpinned ref. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The v1.13 extraction does not preserve symlinks in the native SDK sysroots, causing lld to fail to resolve -lm/-lc and to fall back to static archives during cross-compilation.
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
1 participant
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.
Bumps every action referenced by
.github/workflows/IKVM.ymlto its latest release. Per request, the GitVersion actions are left untouched.Upgraded
actions/checkoutactions/cacheactions/setup-dotnetactions/upload-artifactactions/download-artifactactions/github-scriptVampire/setup-wslrobinraju/release-downloaderncipollo/release-actionjlumbroso/free-disk-space@mainLeft alone
gittools/actions/gitversion/*â excluded by request.andstor/file-existence-action@v3,baptiste0928/cargo-install@v3,whelk-io/maven-settings-xml-action@v22â already on the latest major.pierotofy/set-swap-space@masterâmasteris 4 commits ahead of the only tag (v1.0, 2021), including a fix for hosts with no existing swapfile. Pinning tov1.0would be a regression, so this stays on the floating ref.jlumbroso/free-disk-space'smainandv1.3.1currently point at identical trees, so that change is behavior-neutral and just removes an unpinned branch ref.Notes on breaking changes
Most of these majors are Node 20 â Node 24 runtime bumps plus a CommonJS â ESM migration, both transparent to callers. The workflow already used
checkout@v5/cache@v5/upload-artifact@v6, so the runners already meet the 2.327.1 minimum these versions require. The changes worth a second look:download-artifactv8 now errors on a download digest mismatch instead of warning (digest-mismatchinput, defaults toerror). It also skips unzipping non-zip downloads based onContent-Typeâ irrelevant here since every artifact is uploaded throughupload-artifactand therefore zipped. The v5 path change for single-artifact-by-ID downloads does not apply; all downloads in this workflow are by name.github-scriptv9 breaks scripts thatrequire('@actions/github')or redeclaregetOctokit. The only script here is the three-lineGet Test Namestep, which does neither.checkoutv7 blocks checking out fork PR refs underpull_request_target/workflow_run. This workflow uses plainpull_request, so it is unaffected.setup-dotnetv6 picks up the refreshedinstall-dotnetscripts, which fixes thelink_types[$link_index]: unbound variablefailure installing .NET 10 on themacos-13image (install-dotnet.sh keeps failing to install .NET 10.0.x on macos-13 image actions/setup-dotnet#645). Support for installing 6.0.x/7.0.x is unchanged.Vampire/setup-wslv7 is the one with real behavior change. The step passes no inputs, so it rides the defaults: v3 always used WSLv1 and defaulted to theDebiandistribution, while v6+ always use WSLv2 and v7 defaults toDebian-13(the oldDebianentry was removed). v5+ also only issue the WSL update command on GitHub-hostedwindows-2022, and the test job runs on a customwindows-2025-vs2026label â if that image turns out to lack the WSL2 update, this step will needwsl-version: 1or a pre-step to install it.Not build-validated locally; the workflow run on this PR is the check.