Email feed consumers that a new package has been pushed. Maybe some way of notifying in the Visual Studio Environment?

Currently, you can't view which installed NuGet packages that have updates. If you only have the MyGet feed in Visual Studio and go to the Package Manager there's nothing under the "Updates" tab. But, if you go out to MyGet website and login, click on a NuGet package in your feed, it will display an update.

Currently, only .Net Core 1.x and 2.x are supported.

cannot create an account in the myget service. No account creation is permitted

I would like to be able to set a prerelease package retention policy by number of days. Typically prerelease versions are only pushed by us during a sprint, once completed they are redundant so we would like to set the retention to 30-60 days to ensure old ones are cleaned up even if we don't push new versions of a particular package id for period of time.

How is this possible when all these sites tell a different story?

netcoreapp3.1

Please add support for docker containers

Make sure build services also work for C# 8.

MyGet does not currently support npm audit requests.
NPM can check for outdated packages that have security vulnerabilities.
When using MyGet as a proxy for the default NPM registry, audit does not work.
We are currently in a position where we cannot scope some packages, such that only those packages need the MyGet registry, but also want to use auditing.

Original spec: https://github.com/NuGet/Home/wiki/Packaging-Icon-within-the-nupkg

Example of a package that has this: https://www.myget.org/feed/nettopologysuite/package/nuget/NetTopologySuite (anything with version 2.0.1-pre.181760630 or higher has this)

Note that, in the "Package History" list, packages that use this feature still show up with the generic default icon.

In Github, a table in the readme.md file is displayed with cell borders. In MyGet, the same table is borderless, making it harder to read. Would be nice if MyGet displayed markdown tables showing borders.

Currently only v2 versions are supported for as upstream sources. We are currently reviewing a setup which does not support v2 feeds and this is a blocker...

Under the package retention options, it would be handy to have rules for how long to retain unlisted packages. We run our own retention scripts using nuget.exe to do the delist, but there's no way of having the delisted scripts be cleaned up outside of the same retention rules that apply to all packages.

I would love to see Azure DevOps Yaml Examples

When I try to connect using github authentication, MyGet requests:

Personal user data
Full access
This application will be able to read and write all user data. this includes the following:
Private email addresses
Private profile information
Followers.

This is obviously far too much privilege, and I refuse to authorize myget this level of access.

Supporting Kubernetes Helm chart repositories