Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: fix node20 compatibility issues in e2e pipeline #606

Merged
merged 3 commits into from
Nov 11, 2024

Conversation

maksadbek
Copy link
Collaborator

@maksadbek maksadbek commented Nov 10, 2024

e2e pipeline fails on Ubuntu 16.04 and 18.04 due to the recent default switch to node20 in actions/checkout. Node20 requires GLIBC 2.28 or higher, which these environments lack. To resolve this, we’re setting the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable to allow fallback to a compatible Node version, restoring pipeline stability.

Useful links:

The git checkout step is failing as actions/checkout actions has started
using node20 be default. Since node20 requires GLIBC version 2.28 and
upper, our tests that run on Ubunu 16.04 and 18.04 are failing. The
solution is to add ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true env
variable.
@maksadbek maksadbek added the Type: ci Pull requests that update CI/CD workflows label Nov 10, 2024
@maksadbek maksadbek self-assigned this Nov 10, 2024
Copy link
Member

@derevnjuk derevnjuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please follow the contributing guide: the short description should clearly indicate what was done, while the PR body should explain the purpose of these changes if it’s not obvious from the changes itself. While you used a generic statement for the short description and provided detailed explanations in the body.

E.g.

ci: fix node20 compatibility issues in e2e pipeline

e2e pipeline fails on Ubuntu 16.04 and 18.04 due to the recent default switch to node20 in actions/checkout. Node20 requires GLIBC 2.28 or higher, which these environments lack. To resolve this, we’re setting the `ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true` environment variable to allow fallback to a compatible Node version, restoring pipeline stability.

Useful links:
* [GitHub changelog: node20 default](https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/)
* [GitHub issue #1809](https://github.com/actions/checkout/issues/1809)

.github/workflows/e2e.yml Outdated Show resolved Hide resolved
@maksadbek maksadbek changed the title chore: fix e2e test pipeline ci: fix node20 compatibility issues in e2e pipeline Nov 11, 2024
@derevnjuk derevnjuk enabled auto-merge (squash) November 11, 2024 10:53
@derevnjuk derevnjuk merged commit 714e36e into master Nov 11, 2024
23 of 27 checks passed
@derevnjuk derevnjuk deleted the gh-actions-fix-e2e-tests-workflow branch November 11, 2024 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: ci Pull requests that update CI/CD workflows
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants