Should dll developed as Nuget be placed in separate repository for internal company use?

I was developing an ASP.Net Core Web Api together with dlls specyfic to the domain. I have also developed a dll which turned out to be the one that can be shared across organization as NuGet dll. I created that dll in the same solution where i have my AspNet Core app. In consequence each time I run a build, version of this Nuget is bumbed up even if no changes were made to that dll.

I have 2 questions:

1. Should I move this Nuget dll to separate repository? Is this a best practice?
2. Can i somehow configure a task in AzureDevops pipeline in a way that version should be bumped only when there is a change made to that dll?