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

End-of-Life for Node.js 16 #254

Closed
jalondonot opened this issue Mar 1, 2023 · 9 comments
Closed

End-of-Life for Node.js 16 #254

jalondonot opened this issue Mar 1, 2023 · 9 comments
Assignees
Milestone

Comments

@jalondonot
Copy link

https://nodejs.org/en/blog/announcements/nodejs16-eol/

@jalondonot jalondonot added this to the Palm.1 milestone Mar 1, 2023
@ghassanmas
Copy link
Member

There is also an issue opened for this openedx/platform-roadmap/issues/243 @jmbowman do you have any suggestions or input if FED-BOM is expected to handle this completely?

@jmbowman
Copy link
Contributor

jmbowman commented Mar 8, 2023

The plan is to follow the Upgrade Project Runbook, which is still being revised based on incoming feedback. So issues will be created for the work needed in each repo, and the maintainers of those repos will be consulted regarding how much of the upgrade work they would like to do themselves vs. delegating to FED-BOM. And FED-BOM is encouraged to delegate work to the broader Open edX developer community where appropriate.

@jfavellar90
Copy link

jfavellar90 commented Mar 9, 2023

@jalondonot It seems it requires a lot of work to migrate from Node16 before the Palm cutoff. This issue should be a high priority, what do you think? Should we open a discussion in the OpenedX discuss to define if this is a blocker?

@arbrandes is this something that the frontend working group has on its radar?

@arbrandes
Copy link
Contributor

@jfavellar90, we have it on our radar, yes. It's on the roadmap, as a matter of fact. As you can see there, FED-BOM is tasked with handling it. The intention is to finish it before the Palm cut-off, but they might require help. I asked them to holler if that happens.

In any case, it's worth keeping an eye on that roadmap ticket as the cut-off date nears.

@ghassanmas
Copy link
Member

ghassanmas commented Mar 14, 2023

The issue/ticket though doesn't mention edx-platform, was that intentional?, is it in the scope of the ticket?

@arbrandes
Copy link
Contributor

@ghassanmas, good question. Do you mind adding that question to the roadmap ticket?

@mariajgrimaldi
Copy link
Member

Hi there @arbrandes! Do we know how is this issue going? Let us know!

@jmbowman
Copy link
Contributor

The status in the tasklist of the roadmap issue is accurate: openedx/platform-roadmap#243 . Most of the Node-using repos were already updated to use Node 18 in time for the Palm release. The only stragglers are credentials (in the process of migrating to a new UI and throwing the old one away), edx-platform (blocked by other in-progress maintenance and upgrades), and edx-analytics-dashboard (CI failing with the changes, debugging is in progress). The security impact is relatively minor as these only use Node as a build-time dependency during deployments, and we plan to have more (ideally all) of the stragglers completed in time for the Quince release.

@mariajgrimaldi mariajgrimaldi modified the milestones: Palm.2, Palm.3 Aug 16, 2023
@arbrandes arbrandes modified the milestones: Palm.3, Quince.1 Oct 5, 2023
@cmltaWt0 cmltaWt0 modified the milestones: Quince.1, Quince.2 Jan 8, 2024
@mariajgrimaldi mariajgrimaldi modified the milestones: Quince.2, Quince.3 Feb 12, 2024
@arbrandes
Copy link
Contributor

This has now been superseded by openedx/platform-roadmap#363.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Status: Closed
Development

No branches or pull requests

7 participants