Skip to content

test: Remove support for Node 18#30

Merged
BilalQamar95 merged 1 commit intomasterfrom
bilalqamar95/node20-upgrade-3
Nov 4, 2024
Merged

test: Remove support for Node 18#30
BilalQamar95 merged 1 commit intomasterfrom
bilalqamar95/node20-upgrade-3

Conversation

@BilalQamar95
Copy link

Part of openedx/public-engineering#230.

Description

Completed upgrade to Node 20 by removing the Node 18 CI check and using .nvmrc for version to use.

See openedx/public-engineering#267 for further information.

@BilalQamar95 BilalQamar95 self-assigned this Oct 10, 2024
@github-actions
Copy link

Coverage report

This PR does not seem to contain any modification to coverable code.


RUN nodeenv ${INSIGHTS_NODEENV_DIR} --node=18.20.2 --prebuilt \
&& npm install -g npm@10.5.x
RUN nodeenv ${INSIGHTS_NODEENV_DIR} --node=20.15.1 --prebuilt \
Copy link

@huniafatima-99 huniafatima-99 Nov 4, 2024

Choose a reason for hiding this comment

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

As the Dockerfile has been moved to public-dockerfiles repo, node20 change would be needed there. We can remove this change

Copy link
Author

Choose a reason for hiding this comment

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

This Node 20 update is required because the PR drops support for Node 18, and the Dockerfile is still active in this project. There’s a separate PR to remove the Dockerfile, it’s pending due to CI failures, for now Dockerfile is still part of this project and utilized in CI, aligning it with the Node version specified in the PR is necessary to ensure compatibility and prevent CI failures. Once that PR is merged and the Dockerfile is gone this won't matter, until then for as long as Dockerfile continues to exist, this change is relevant and essential.

@BilalQamar95 BilalQamar95 merged commit 806013d into master Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants