-
Notifications
You must be signed in to change notification settings - Fork 474
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
Feature: Remove Sonatype Lift from Dependency-Update-Tool check #3559
Comments
Hi hayley! Thanks for sharing that info. I'm leaving a +1 here to remove Sonatype both from the documentation and code as a valid Dependency-Update-Tool. I'm in a triager role so let's wait to see what the maintainers and other users think. |
Removing from the checks documentation seems like something that can be done immediately. Removing the code is a use case to consider for structured results and deprecated probes. @laurentsimon what do you think from a probe perspective?
Since we haven't released probes yet, it's not like anyone has a policy on it yet. I think 3 works. If probes were released, I think either 1 or 2 could be viable options. |
Option 2 could pass along a deprecation notice as well. If we wanted an OutcomeDeprecated or something? |
(3) works for me too. |
Is your feature request related to a problem? Please describe.
Sonatype Lift has been retired, but it still shows up as a dependency update tool option.
Describe the solution you'd like
I don't know if projects that had installed Sonatype Lift are still getting scores that reflect using a tool, but if they are that should probably be changed. A good first step would be to remove Sonatype Lift from the documentation, which currently has a dead link.
I'm not sure if this is better suited for a bug report or a feature request. Apologies if this ended up in the wrong bucket.
The text was updated successfully, but these errors were encountered: