I have a solution with 10 projects, I used to distribute this as an SDK with an installer back in the day.
To change that in VSTS I added the steps to create a package per project, every time I make a change, a build is triggered and a PS script change the version of the nuspec files, in the end the packages are pushed to a feed, if I made a change to just one project the build pushes a new version of every packages even though there are no changes in all of them.
Someone told me this was wrong, I should not push a new version if there was no change in the package and every package has to be created separately.
That makes sense, but in my case, I have to create 9 more builds in VSTS, replace the project references for nuget dependencies, and, if I ever need to change two projects I have to modify one, commit the change, then open the second project update the nuget reference and make the change, which seems like a lot of extra work.
So my question is, is there a best practice or recommendation about the flow in creating a group of nuget packages?