Update Node to 20.9.0 LTS and bugfix npm eacces error #122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jujaga
added
bug
jujaga
requested review from
jatindersingh93,
wilwong89,
kamorel,
TimCsaky and
norrisng-bc
Signed-off-by: Jeremy Ho <[email protected]>
jujaga
force-pushed
the
bugfix/npm-eacces
branch
from
bf02275 to
f6f9431
Compare
|
PR Deployed at: https://ches-dev-pr-122.apps.silver.devops.gov.bc.ca |
TimCsaky
approved these changes
Dec 12, 2023
kyle1morel
approved these changes
Dec 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses an operational issue where the
/.npmroot cache has problems being accessed by npm which is now preventing new pods from spinning up on Openshift. Also bumps Node from 16 to 20 LTS.Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist
v*.api-spec.yamldocumentation (if appropriate)Further comments