Renovate loses ".npmrc" context when trying to regenerate lock files #8939
Unanswered
elliotleelewis
asked this question in
Request Help
Replies: 1 comment 30 replies
-
Do you have any |
Beta Was this translation helpful? Give feedback.
30 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What Renovate type, platform and version are you using?
Self-hosted in Azure DevOps. Using packages from both NPMJS and a private feed in Azure DevOps (Azure Artifacts)
Describe the bug
Renovate is trying to create a PR for a private NPM package, but falls over itself when generating the lock-file, and gets a "401 Unauthorized" from the private feed.
I'm setting the "npmrc" config option via a command-line parameter to the Renovate runner with the following value (of course with the new lines replaced by "\n"):
We use this same ".npmrc" file everywhere across our organization and I know that it works. It even works here to allow Renovate to access the info about the updated package, just not sure why it doesn't want to use this when it generates the lock-file. Maybe its getting overwrote by something?
Relevant debug logs
Have you created a minimal reproduction repository?
Please read the minimal reproductions documentation to learn how to make a good minimal reproduction repository.
Additional context
Really not sure if I have any additional context here, I've tried to give as much detail as I can in the logs. My only theory is that from the debug logs it looks like Renovate is using the
.npmrc
from the branch, rather than the one from my Renovate config.Beta Was this translation helpful? Give feedback.
All reactions