#53451: ci: use a download-artifact fork that doesn't parse the event file at import
Description of Change
The two download-artifact steps in the test job's parallel: setup group have failed main four times since mid-August (08-18, 08-20, 08-27, 09-01) with
SyntaxError: Expected double-quoted property name in JSON at position 8192
at new Context (.../download-artifact/dist/index.js)
before downloading anything. Cause: actions/runner rewrites $GITHUB_EVENT_PATH at the start of every step (ExecutionContext.WriteWebhookPayload), and @actions/github's Context constructor — which runs at import in any action that depends on it, download-artifact included via @actions/artifact — reads and parses that file eagerly. Inside a parallel group a sibling step starting at the wrong moment hands it a half-written file. Sequential steps never hit this, which is why it only appeared once the group was introduced.
This points those two steps at a fork of download-artifact v8.0.1 whose only change is to read the payload lazily (with a short retry on a parse error). download-artifact never reads the payload — run id and repo come from inputs/env — so in practice the file is no longer touched at all. The steps stay parallel; everything else about the action (retries, digest verification) is unchanged. The runner-side fix is filed separately; once a runner release stops rewriting the file per step this can go back to upstream.
Checklist
- I have built and tested this change
- I have filled out the PR description
- I have reviewed and verified the changes
Release Notes
Notes: none
Backports
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron