Best practices to keep track of dependencies on code in private NuGet package

Within several projects I worked in, there would be one or more NuGet packages in a private feed for common code.

When just adding new functions / classes to these NuGet packages there is no issue, but when you want to remove or refactor methods then you would like to know

• what projects (consuming the private NuGet package) need to be updated / refactored as well
• what code in the private NuGet package might actually have become redundant (so that it can be removed immediately)

I'm wondering what practices people have to keep track of this?

Options I could think of are:

• maintaining a "mega solution" (a solution containing all projects of your team) containing your NuGet project as a ProjectReference instead of as a PackageReference so that you can use Visual Studios reference tracking features (see below)
• just doing the refactoring you want in the private NuGet, publishing it as a new version and fixing the consuming projects when they update to the new version