Bug 2178088

Summary: nodejs:18/nodejs: Rebase to the latest Nodejs 18 release [rhel-9] [rhel-9.2.0.z]
Product: Red Hat Enterprise Linux 9 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: nodejsAssignee: Zuzana Svetlikova <zsvetlik>
Status: CLOSED ERRATA QA Contact: Jan Houska <jhouska>
Severity: unspecified Docs Contact: Lenka Špačková <lkuprova>
Priority: unspecified    
Version: unspecifiedCC: pasik, zsvetlik
Target Milestone: rcKeywords: Rebase, Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
.`nodejs:18` rebased to version 18.14 with `npm` rebased to version `9` The updated `Node.js 18.14` includes a SemVer major upgrade of `npm` from version 8 to version 9. This update was necessary due to maintenance reasons and may require you to adjust your `npm` configuration. Notably, auth-related settings that are not scoped to a specific registry are no longer supported. This change was made for security reasons. If you used unscoped authentication configurations, the supplied token was sent to every registry listed in the `.npmrc` file. If you use unscoped authentication tokens, generate and supply registry-scoped tokens in your `.npmrc` file. If you have configuration lines using `_auth`, such as `pass:[//registry.npmjs.org/:_auth]` in your `.npmrc` files, replace them with `pass:[//registry.npmjs.org/:_authToken=${NPM_TOKEN}]` and supply the scoped token that you generated. For a complete list of changes, see the link:https://nodejs.org/en/blog/release/v18.14.0#updated-npm-to-931[upstream changelog].
 Story Points: ---
Clone Of: 2159389 Environment:
Last Closed: 2023-05-09 11:46:59 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: 2159389    
Bug Blocks:    

Comment 10 errata-xmlrpc 2023-05-09 11:46:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: nodejs:18 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:2654