-
Notifications
You must be signed in to change notification settings - Fork 644
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
Flow deprecation and vulnerability info into search service #7297
Comments
Likely not needed for MVP. |
removing out of the Epic, since it covers only the MVP. |
Once this is fixed, we'd appreciate a heads up so we can fix the NuGet.Client side experience: NuGet/Home#8719 |
This is a blocker for NuGet/Home#8058. |
Is this on any roadmap as of now? |
Nope, not scheduled right now. Let's talk offline with @skofman1 about when this could happen w.r.t. to our other commitments. |
@nkolev92, since this is needed for an e2e experience (client perf improvement) we need to align priorities & schedules between the teams. i.e., how high is NuGet/Home#8058 on the client team backlog? Right now I see it marked as P3. We can discuss further offline. |
Sounds good. I think the first target would be: NuGet/Home#10865. I've started a discussion to prioritize that issue from a client perspective. Thanks @joelverhagen @skofman1! |
Can we merge this? Or does it still need docs and rebuilt index? |
Package deprecation info needs to flow into search service.
Required for phase 2 of package deprecation PMUI and more advanced search filtering.
Required for displaying deprecation and vulnerability information in NuGet.org search results page.
general:
v3 search endpoint:
v2 search endpoint:
NuGet.org:
The text was updated successfully, but these errors were encountered: