Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecation Issue not created #6478

Closed
dword-design opened this issue Jun 9, 2020 · 5 comments
Closed

Deprecation Issue not created #6478

dword-design opened this issue Jun 9, 2020 · 5 comments
Labels
duplicate This issue is closed as a duplicate of another issue

Comments

@dword-design
Copy link

What Renovate type are you using?

Hosted App with GitHub

Describe the bug
I create a Node.js project with a deprecated dependency. After pushing, I expect that an issue with a deprecation warning is created.

Did you see anything helpful in debug logs?
In the logs I see that the deprecation is detected, but it doesn't lead to a warning.

To Reproduce
I built a minimal example here:
https://github.com/dword-design/test-deprecation
I tried both the base config and explicitly setting suppressNotifications to an empty array, but nothing helped.

Additional context

@rarkins
Copy link
Collaborator

rarkins commented Jun 10, 2020

Depreciation issues in the app are currently disabled due to a previous bug we encountered. I’ll look int testing and enabling them again

@viceice viceice added #internal priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others labels Jun 10, 2020
@dword-design
Copy link
Author

@rarkins ah ok. Would be great to have this feature enabled again!

@rarkins rarkins removed the ready label Jun 18, 2020
@dword-design
Copy link
Author

@rarkins Does this bug only exist in the app or also in the self-hosted tool?

@rarkins
Copy link
Collaborator

rarkins commented Jul 11, 2020

I observed them in the app, and they may have been only in the app, but I can't be sure. It was related to subtle differences in how the GitHub API filtering worked when giving it a "real" user vs app pseudo-user. Renovate wanted to say "give me issues I created" but it behaved differently.

@rarkins
Copy link
Collaborator

rarkins commented Dec 19, 2021

Duplicate of #5098

@rarkins rarkins marked this as a duplicate of #5098 Dec 19, 2021
@rarkins rarkins closed this as completed Dec 19, 2021
@HonkingGoose HonkingGoose added duplicate This issue is closed as a duplicate of another issue and removed type:bug Bug fix of existing functionality priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:ready labels Dec 20, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue is closed as a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

4 participants