CI at Wikimedia was apparently updated to Node 18.20.2 on April 16.
My understanding is Fresh is meant to mirror CI, so it seems we're due for an update.
See also T331180: Upgrade all CI jobs for WMF-deployed projects from Node 16 to Node 18
Previously:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T362908 Update Fresh's version of Node 18 from 18.17.0 to 18.20.2 | |||
| Resolved | Jdforrester-WMF | T331181 Create WMF CI images and jobs for Node.js 18 |
To RelEng: The way we usually structure these tasks is to link to the previous one for the same purpose (Fresh) and track "Create image" as the subtask.
Usually we try to time it so that Fresh CI includes and releases the next image as soon as it is created, before it is widely adopted, so that by the time you're debugging CI failures you already have your local upgraded and may be even have tested your project with the next version already. Taking note that fresh-node ships multiple versions named like fresh-nodeXX so the caller decides which one they use either way. The default tends to be the middle version (i.e. the one powering most jobs today).