ci: pin the Windows runner to windows-2022 - #85
Merged
Conversation
The `windows-latest` label has rolled over to Windows Server 2025, whose image
no longer ships the Visual Studio C++ toolchain node-gyp requires. Every Windows
build now fails in electron-builder's install-app-deps while rebuilding node-pty:
Error: Could not find any Visual Studio installation to use
⨯ node-gyp failed to rebuild '...\node_modules\node-pty' failedTask=installAppDeps
Pinning to windows-2022 restores an image that still carries the toolchain.
This went unnoticed because build.yml only runs on pull_request and v* tags —
never on push to main — and fork PRs sit at action_required, so no run had
actually executed in some time.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
abasiri
added a commit
to Flaykz/switchboard
that referenced
this pull request
Aug 1, 2026
Only conflict was .github/workflows/build.yml: this branch pinned the Windows runner to windows-2022, and doctly#85 landed the same fix on main (credited to @Flaykz, who found it independently) with a fuller comment explaining the Windows Server 2025 toolchain removal. Took main's version, so the line is identical and no longer carried here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
abasiri
pushed a commit
that referenced
this pull request
Aug 1, 2026
Adds two gauges to the status bar: session context usage (read from the tail of the session .jsonl via a new get-session-tokens IPC handler) and 5-hour quota usage (via the existing get-usage handler), with the quota gauge linking to the Stats tab. The windows-2022 runner pin from this branch landed separately as #85. Co-authored-by: Flaykz <flaykz@users.noreply.github.com>
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.
windows-latesthas rolled over to Windows Server 2025, whose image no longer ships the Visual Studio C++ toolchainnode-gypneeds. Every Windows build fails in electron-builder'sinstall-app-depswhile rebuildingnode-pty:Observed on run 30686024328, triggered by a push to #55. macOS passed in the same run, so this is Windows-image-specific, not a code problem.
Pinning to
windows-2022restores an image that still carries the toolchain.Why this went unnoticed
build.ymltriggers only onpull_requestandv*tags — never on push tomain— and recent fork PRs are all parked ataction_requiredpending maintainer approval. So no run had actually executed in a while, and the last green Windows runs predate the image rollover. Worth considering separately: addingpush: branches: [main]so regressions surface on merge rather than on whichever PR happens to trigger a run.Credit
@Flaykz spotted this independently and included the same pin in #72. Pulling it out here so it lands on its own merits and #72 can stay focused on the status-bar gauges.
🤖 Generated with Claude Code