Summary
Staging/PR CI logs repeatedly warn that several actions still run on Node.js 20. GitHub says actions will be forced to Node.js 24 by default starting 2026-06-16 and Node.js 20 will be removed from the runner on 2026-09-16.
Evidence
Observed on staging CI run after PR #692 merge: https://github.com/MINT-IA/MINT/actions/runs/26816593773
Warnings mention actions such as:
actions/checkout@v4actions/setup-python@v5dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36
Impact
CI may become noisy or brittle around GitHub runner runtime migration. This is separate from TestFlight certificate auth issue #691.
Suggested next step
Audit workflow actions for Node 24-compatible versions or set an explicit migration strategy before 2026-06-16. Keep this as CI reliability work, not app feature work.
Summary
Staging/PR CI logs repeatedly warn that several actions still run on Node.js 20. GitHub says actions will be forced to Node.js 24 by default starting 2026-06-16 and Node.js 20 will be removed from the runner on 2026-09-16.
Evidence
Observed on staging CI run after PR #692 merge: https://github.com/MINT-IA/MINT/actions/runs/26816593773
Warnings mention actions such as:
actions/checkout@v4actions/setup-python@v5dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36Impact
CI may become noisy or brittle around GitHub runner runtime migration. This is separate from TestFlight certificate auth issue #691.
Suggested next step
Audit workflow actions for Node 24-compatible versions or set an explicit migration strategy before 2026-06-16. Keep this as CI reliability work, not app feature work.