Bug 2087185

Summary:	Node.js 18.x by default
Product:	[Fedora] Fedora	Reporter:	Ben Cotton <bcotton>
Component:	Changes Tracking	Assignee:	Stephen Gallagher <sgallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	37	CC:	bcotton, sgallagh
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-15 16:22:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2016049

Description Ben Cotton 2022-05-17 14:17:06 UTC

This is a tracking bug for Change: Node.js 18.x by default
For more details, see: https://fedoraproject.org/wiki/Changes/Nodejs18

The latest release of Node.js to carry a 30-month lifecycle is the 18.x series. As with 16.x, 14.x, 12.x, 10.x and 8.x before it, Fedora 37 will carry 18.x as the default Node.js interpreter for the system. The 16.x, and 14.x interpreters will remain available as non-default module streams.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Stephen Gallagher 2022-05-17 20:12:11 UTC

The packaging work is done and it's just waiting for June 6th to make the cut over to 18.x.

Comment 2 Ben Cotton 2022-08-09 16:02:52 UTC

Today we reached the Code Complete (Testable) milestone on the F37 schedule: https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html

At this time, all F37 Changes should be complete enough to be testable. You can indicate this by setting this tracker to the MODIFIED status. If the Change is 100% code complete, you can set the tracker to ON_QA. If you need to defer this Change to F38, please NEEDINFO me.

Changes that have not reached at least the MODIFIED status will be given to FESCo for evaluation of contingency plans.

Comment 3 Ben Cotton 2022-08-10 16:58:08 UTC

nodejs-18 appears to be in the repo (although dist-git says the F37 version is a nonsensical nodejs-10.2.154.13-1.18.7.0.1.fc37). Setting to ON_QA.

Comment 4 Stephen Gallagher 2022-08-15 13:08:35 UTC

(In reply to Ben Cotton from comment #3)
> nodejs-18 appears to be in the repo (although dist-git says the F37 version
> is a nonsensical nodejs-10.2.154.13-1.18.7.0.1.fc37). Setting to ON_QA.

Where are you seeing that? https://src.fedoraproject.org/rpms/nodejs shows nodejs-18.7.0-1.fc37

Comment 5 Ben Cotton 2022-08-15 13:26:43 UTC

(In reply to Stephen Gallagher from comment #4)
> (In reply to Ben Cotton from comment #3)
> > nodejs-18 appears to be in the repo (although dist-git says the F37 version
> > is a nonsensical nodejs-10.2.154.13-1.18.7.0.1.fc37). Setting to ON_QA.
> 
> Where are you seeing that? https://src.fedoraproject.org/rpms/nodejs shows
> nodejs-18.7.0-1.fc37

It didn't when I looked the other day, but I agree it looks correct now. Shrug.

Comment 6 Ben Cotton 2022-11-15 16:22:28 UTC

F37 was released today, so I am closing this tracker. If this Change was not completed, please notify me ASAP.