You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub Action’s just started enforcing the long-announced EOL on Node16-based actions. Basically, the latest release of GHA’s Runner agent ignores the fact that an action is requesting node16, and instead just calls node20 anyway.
Until now, we were relying on GLIBC 2.24 Docker images or runners in very specific places to ensure that the native artifacts included in our official SDK releases would run on some older Linux distros that some of our customers were still using.
However, given that Node20 is incompatible with GLIBC 2.27 or earlier, this no longer works, and our CI workflows are now failing.
The text was updated successfully, but these errors were encountered:
Describe the bug
GitHub Action’s just started enforcing the long-announced EOL on Node16-based actions. Basically, the latest release of GHA’s Runner agent ignores the fact that an action is requesting node16, and instead just calls node20 anyway.
Until now, we were relying on GLIBC 2.24 Docker images or runners in very specific places to ensure that the native artifacts included in our official SDK releases would run on some older Linux distros that some of our customers were still using.
However, given that Node20 is incompatible with GLIBC 2.27 or earlier, this no longer works, and our CI workflows are now failing.
The text was updated successfully, but these errors were encountered: