Back to bug 2178088
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-03-14 11:25:53 UTC | Pool ID | sst_cs_apps_rhel_9 | |
| Red Hat One Jira (issues.redhat.com) | 2023-03-27 10:26:31 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-153144 | |
| Zuzana Svetlikova | 2023-03-28 14:31:16 UTC | QA Contact | rhel-cs-apps-subsystem-qe | jhouska |
| Status | NEW | MODIFIED | ||
| errata-xmlrpc | 2023-03-28 14:47:54 UTC | Status | MODIFIED | ON_QA |
| Jan Houska | 2023-03-30 12:17:26 UTC | Status | ON_QA | VERIFIED |
| Lenka Špačková | 2023-04-18 10:58:20 UTC | Docs Contact | lkuprova | |
| Doc Type | Rebase: Bug Fixes and Enhancements | 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` like `//registry.npmjs.org/:_auth` in your `.npmrc` files, replace them with `//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]. |
|||
| Lenka Špačková | 2023-04-18 11:41:41 UTC | 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` like `//registry.npmjs.org/:_auth` in your `.npmrc` files, replace them with `//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]. | .`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` like `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]. |
| Lenka Špačková | 2023-04-18 12:08:38 UTC | 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` like `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]. | .`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]. |
| errata-xmlrpc | 2023-05-09 00:41:24 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-05-09 11:46:59 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-05-09 11:46:59 UTC | |||
| errata-xmlrpc | 2023-05-09 11:47:35 UTC | Link ID | Red Hat Product Errata RHSA-2023:2654 | |
| Pasi Karkkainen | 2023-05-14 13:25:19 UTC | CC | pasik |
Back to bug 2178088