"Preset package is missing a renovate-config entry" using Github Package Registry #8266
Replies: 4 comments 10 replies
-
And, as mentioned there, it seems to be due to GH packages seemingly limiting metadata to certain fields. See, e.g., |
Beta Was this translation helpful? Give feedback.
-
One workaround would be to actually grab the package and its Is there any config option we could use to trick Renovate into downloading the renovate-config package from NPM but have the |
Beta Was this translation helpful? Give feedback.
-
Testing out using the
This gives me this error:
If I take out the |
Beta Was this translation helpful? Give feedback.
-
ps - we do have a confirmation from GHE support that this is currently a limitation (as far as NPM packages go), so just in case this comes up for someone else. Frankly, it wasn't something we imagined would be an issue. I'm not sure if other artifact repositories that implement an NPM type interface also have a similar limitation or not.
|
Beta Was this translation helpful? Give feedback.
-
We are switching from npmjs to Github Package Registry for npm packages, and are now encountering this error from self-hosted renovate (version 1.2.0):
Preset package is missing a renovate-config entry (@orgName)
Our
@orgName/renovate-config
repo has a "renovate-config" section in its package.json, plus it worked before the registry change.This continues the discussion started here mend/renovate-ce-ee#130.
Beta Was this translation helpful? Give feedback.
All reactions