- Issue created by @lauriii
- Status changed to Needs review
almost 2 years ago 9:22pm 25 January 2023 - 🇫🇮Finland lauriii Finland
Posting a patch to see what DrupalCI thinks about this.
- Status changed to Postponed
almost 2 years ago 10:56pm 25 January 2023 - 🇬🇧United Kingdom longwave UK
This will need an infrastructure issue to bump the DrupalCI containers to use Node 18.
- Status changed to Active
over 1 year ago 7:33pm 31 March 2023 - 🇬🇧United Kingdom longwave UK
Opened #3351615: Update nodejs to v18 → in the testbot queue for this.
- 🇫🇷France andypost
Needs to solve infra issue first #3351615: Update nodejs to v18 →
- last update
over 1 year ago 29,378 pass - Status changed to Needs work
over 1 year ago 10:52pm 5 May 2023 - 🇺🇸United States smustgrave
Only moving to NW for the change record.
- Status changed to Needs review
over 1 year ago 3:41pm 6 May 2023 - 🇬🇧United Kingdom longwave UK
Change record: https://www.drupal.org/node/3358623 →
Also added a release note.
- Status changed to RTBC
over 1 year ago 3:53pm 6 May 2023 - last update
over 1 year ago 29,379 pass -
lauriii →
committed 7d31a390 on 10.1.x
Issue #3336535 by lauriii, andypost, longwave: Require Node.js 18 for...
-
lauriii →
committed 7d31a390 on 10.1.x
- Status changed to Fixed
over 1 year ago 7:20am 8 May 2023 Automatically closed - issue fixed for 2 weeks with no activity.
