fix: update CI workflows to use current runner and action versions#10863
Open
BenJule wants to merge 1 commit into
Open
fix: update CI workflows to use current runner and action versions#10863BenJule wants to merge 1 commit into
BenJule wants to merge 1 commit into
Conversation
- Replace deprecated windows-latest runner with windows-2025 across build_all, build_bambu, build_check_cache, build_deps, build_ubuntu, winget_updater (windows-latest redirects to windows-2025-vs2026 on June 15 2026, so explicit pin avoids the redirect) - Replace ubuntu-20.04 runner with ubuntu-22.04 in build_ubuntu (ubuntu-20.04 was removed from GitHub-hosted runners in April 2025) - Fix podman buildx build → podman build in build_ubuntu (podman has no buildx subcommand; the command failed at runtime) - Update microsoft/setup-msbuild@v2 → @V3 in build_bambu and build_deps (@v2 depends on deprecated Node.js 20 runner) - Fix push trigger branch main → master in build_all; the repo default branch is master so the workflow never fired on push - Fix refs/heads/main → refs/heads/master in build_bambu mac-artifact condition (condition was always true, zipping on every push) - Pin winget-releaser@main → @v2 in winget_updater (floating @main is not reproducible; @v2 is the current stable release) - Remove duplicate 'brew unlink python3' call in build_deps
Contributor
Author
|
Apologies — this PR was closed by mistake on 2026-06-07, and that was an error on my side, not a deliberate decision to withdraw the change. It happened as an unintended side effect of a branch cleanup in my fork: deleting the head branch automatically closed this PR. The contribution still stands. I have restored the branch and reopened the PR. Sorry for the noise and any confusion this caused. |
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.
Summary
Several workflows reference deprecated or removed runners and actions:
windows-latest→windows-2025(build_all, build_bambu, build_check_cache, build_deps, winget_updater) — redirects to windows-2025-vs2026 on June 15 2026ubuntu-20.04→ubuntu-22.04(build_ubuntu) — ubuntu-20.04 was removed in April 2025, workflow fails immediatelypodman buildx build→podman build(build_ubuntu) — podman has no buildx subcommand, fails at runtimemicrosoft/setup-msbuild@v2→@v3(build_bambu, build_deps) — v2 uses deprecated Node.js 20branches: main→branches: master(build_all push trigger) — repo default branch is master so workflow never fired on pushrefs/heads/main→refs/heads/master(build_bambu mac-artifact condition) — condition was always true, zip created on every pushwinget-releaser@main→@v2(winget_updater) — floating @main pin replaced with stable releasebrew unlink python3in build_depsTest plan
windows-latestcurrently resolves towindows-2025so the swap is like-for-likeubuntu-22.04is used by all other Linux steps in the build chain