Punycode deprecation causing super-linter to fail #29029
Replies: 2 comments 2 replies
-
I don't see how this is a Renovate bug. punycode is used throughout a number of eslint packages, which Renovate uses in devDependencies. |
Beta Was this translation helpful? Give feedback.
2 replies
-
I did not notice the migrateConfig notification within the linter, this fixed the issue. Thank you for your time. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
I think I found a bug
How are you running Renovate?
Mend Renovate hosted app on github.com
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitHub
Please tell us more about your question or problem
We use super-linter in our github actions to validate configurations of renovate. Recently it has started failing when using the renovate-config-validator binary in it's runs.
Running locally allows us to validate that the config is valid, but it does produce a warning at the start of execution that shows renovate is using the deprecated punycode package.
Is there an alternative as requested in the error logs attached that we can use?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions