Skip to content

Bump GitHub Actions to v5 to fix Windows checkout flakiness#23

Open
bryanroscoe wants to merge 1 commit into
mainfrom
fix/failing-tests
Open

Bump GitHub Actions to v5 to fix Windows checkout flakiness#23
bryanroscoe wants to merge 1 commit into
mainfrom
fix/failing-tests

Conversation

@bryanroscoe
Copy link
Copy Markdown
Owner

Root cause

The Tests workflow on main went red after PR #20 merged. Looking at the failed run for commit `46cf06c`, the failure is not in our Pester tests — it's in `actions/checkout@v4` itself on the windows-latest runner:

```
fatal: Cannot prompt because user interactivity has been disabled.
fatal: could not read Username for 'https://github.com': terminal prompts disabled
```

That's a known transient on the Windows runner image when checkout@v4 (Node.js 20) hits a particular auth state during `git fetch`. The same CI run produced GitHub's deprecation warning that Node 20 actions are flipping to Node 24 by default in June 2026 and being removed in September 2026.

Fix

Bump both pinned actions in `.github/workflows/tests.yml` to v5 (Node 24):

  • `actions/checkout@v4` → `@v5` (both job blocks)
  • `actions/upload-artifact@v4` → `@v5`

Verification

  • Local `make test` (current main + this branch): 121 passed / 4 skipped / 0 failed — the code was fine all along; the CI runner was the failure surface.
  • CI will run on this PR (the workflow triggers on changes under `.github/workflows/`) — that's the actual check that matters here.
  • Future deprecation noise from Node 20 → 24 is also resolved by the same bump.

Workflow-file-only change. No code, no test changes.

The Tests run on PR #20's merge commit (46cf06c) failed on the
windows-latest job — not in our Pester tests, but in `actions/checkout@v4`
itself, with:

    fatal: could not read Username for 'https://github.com':
    terminal prompts disabled

This is a known transient on the Windows runner image when checkout@v4
(Node.js 20) hits a particular auth state during `git fetch`. The same
CI run produced a deprecation warning that Node 20 actions are being
phased out (default flip to Node 24 in June 2026, full removal in
September 2026).

Bump both pinned actions to v5 (Node 24):
- actions/checkout@v4 → v5  (both job blocks)
- actions/upload-artifact@v4 → v5

Local Pester run is 121 passed / 4 skipped / 0 failed — the code is
fine, the CI was wrong. This patch is workflow-only.
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.

1 participant