[FOLIO-3576] discuss a process for regular NodeJS version updates Created: 08/Sep/22 Updated: 10/May/23 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Zak Burke | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps Sprint 160 |
| Development Team: | FOLIO DevOps |
| RCA Group: | TBD |
| Description |
|
Summary: Discuss a process for updating stripes modules' node versions on an ~annual basis. Node LTS releases last about 18 months (although the node v16 EOL date was pulled forward by seven months, from 2024-04 to 2023-09, for security reasons), which means we need to update at least that often. With > 60 repos and the node version hard-coded into each repo's workspace config files, that could be a lot of regular churn. One topic of discussion at #stripes-architecture was if/how we could leverage the project-wide templates to bump to v18 without making PRs in every single UI repo as we did for FOLIO-3432. e.g. since we anticipate that most repos will upgrade without problems, is it possible to configure repos with a setting like NODEJS_VERSION: DEFAULT_CI_NODEJS_VERSION so we only have to maintain those settings in once place, allowing repos to receive the change automatically? If a change in that default causes problems from some repos (as we saw when bumping node from 14 to 16 in a few repos) they could pin to a specific version until the problems are fixed, e.g. with: NODEJS_VERSION: 16 We are happy to discuss options. We just want to get the discussion started early so we don't find ourselves under pressure a year from now when v16 is EOLed and stops receiving security updates. |