Repository navigation
fix(ci): keep Cypress readiness checks working on Node 24 - #4387
Conversation
Runner 2.338.0 upgrades the action runtime from Node 24.19.0 to 24.21.0. The got@11 client in Cypress action v7.3.0 crashes on an initial refused connection with Node 24.20.0 and later, before http-server can start. Update all three action references to SHA-pinned v7.4.4, which fixes the readiness check by upgrading got. Upstream: cypress-io/github-action#1874
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Description
Cypress CI can now wait for the frontend server to start on GitHub runner 2.338.0. That runner upgrades the action's Node runtime from 24.19.0 to 24.21.0, exposing a bug in the HTTP client bundled with Cypress action v7.3.0. The readiness check fails immediately with
Socket closed before the connection was established, before tests run.Update all three action references to SHA-pinned v7.4.4, which includes the upstream fix. Both main and release/v4.35 use the affected pin.
Related Issue(s)
Verification/QA
Manual functionality testing
Automated tests
UU/WCAG (follow these guidelines until we have our own)
User documentation @ altinn-studio-docs
Has been added/updated
No functionality has been changed/added, so no documentation is needed
I will do that later/have created an issue
Support in Altinn Studio
Issue(s) created for support in Studio
This change/feature does not require any changes to Altinn Studio
Sprint board
Labels
kind/*andbackport*label to this PR for proper release notes groupingSummary by CodeRabbit