Bug 2228939

Summary: nodejs:18/nodejs: Rebase to the latest Nodejs 18 release [rhel-8]
Product: Red Hat Enterprise Linux 8 Reporter: Vít Ondruch <vondruch>
Component: nodejsAssignee: Jan Staněk <jstanek>
Status: CLOSED MIGRATED QA Contact: Jan Houska <jhouska>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: jhouska
Target Milestone: rcKeywords: MigratedToJIRA, Rebase, Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
: 2234409 (view as bug list) Environment:
Last Closed: 2023-09-20 15:54:56 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: 2234409    

Description Vít Ondruch 2023-08-03 17:13:25 UTC
Nodejs 18.17.0 is now available. Please consider updating.

Comment 1 Vít Ondruch 2023-08-14 14:00:09 UTC
Nodejs 18.17.1 is now available. Please consider updating.

Comment 5 RHEL Program Management 2023-09-20 15:06:54 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-20 15:54:56 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.