How to create GitHub issues for NPM deprecation notices #28815
Unanswered
p5
asked this question in
Request Help
Replies: 1 comment 1 reply
-
We essentially disabled this feature as long ago there was occasional "spam" problems with too many issues raised, people not understanding it, etc. I think that one issue per deprecated dependency is probably too noisy. How about listing them in the Dependency Dashboard issue? |
Beta Was this translation helpful? Give feedback.
1 reply
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 would like help with my configuration
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.
No response
Please tell us more about your question or problem
I would like to have GitHub issues created when a package I am using is marked as "deprecated" in NPM.
After reading the docs, we believe all we should need to do is set
suppressNotifications
to an empty array, since it defaults to["deprecationWarningIssues"]
(see docs).After changing this setting, we are able to see Renovate identifying the deprecation notice in the logs, however no issues are being created, nor are any errors being shown in the job logs.
This package is directly mentioned in my
package.json
as adependency
, but is also a sub-dependency of other packages I am using.Here is Renovate's outputs for the package that I expect to have created the issue.
And please see my current configuration below:
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions