Give the CI test job 50 minutes so Windows can finish

[Mikola Lysenko (mikolalysenko)]

The test job's Windows leg keeps hitting its 35-minute limit with every test passing, so this raises the limit to 50 minutes.

Why

• Green runs leave little headroom: Windows test runs today took 25–32 minutes.
• Slow runners cross the limit: on slower runners, the build step alone ran 4–5 minutes longer than usual. That pushed the job past 35 minutes before the last test binary (core unit tests, about 3 minutes) could finish.
• Recent timeouts:
  • Match Composer patch versions like Composer does #270's head 8b885839: cancelled at 35m16s–35m17s on all three attempts. No test failed, and the new tests passed on Windows.
  • release/v5-prerelease: the same timeout today, 17:37–18:12.

Change

• .github/workflows/ci.yml, test job: timeout-minutes: 35 → 50. It's the only change.
• Nothing else pins this value.
• Linux and macOS are unaffected in practice, because they finish well under the limit.

🤖 Generated with Claude Code

---

Note

Low Risk
Workflow-only timeout tweak; no application or test logic changes.

Overview
Raises the test job timeout in .github/workflows/ci.yml from 35 to 50 minutes for the ubuntu / macOS / Windows matrix.

This targets Windows legs that were hitting the limit with all tests passing—often after slower builds left no time for the last binaries—without changing test steps or other jobs.

^{Reviewed by Cursor Bugbot for commit e63816a. Configure here.}