How avoid creating the version of a nuget package if a nuget package with identical source code is already uploaded to the nuget repository? [closed]

I am using .nuke build to compile my .net core libraries and create nuget packages for them.
To create a version of packages in nuke.build there is a convenient function DotNetPack that allows you to create a NuGet package and specify for it using the .SetVersion function, for version calculations I use GitVersion, namely I read the version like this:
GitVersion.NuGetVersionV2, here is an example of such code

        DotNetPack(_ => _        .SetProject(Solution)        .SetNoBuild(InvokedTargets.Contains(Compile))        .SetConfiguration(Configuration)        .SetOutputDirectory(PackageDirectory)        .SetVersion(GitVersion.NuGetVersionV2)        );

When I create a new commit, the versions of all my nuget packages change
For example:

LibA.0.1.0-task-777-0005.nupkgLibB.0.1.0-task-777-0005.nupkgLibС.0.1.0-task-777-0005.nupkg

How can I avoid creating the new version of a nuget package if a nuget package of .net core library with identical source code is already uploaded to the nuget repository?

My ultimate goal: to reduce the number of generated nuget packages that do not carry new changes in source code and ultimately save space in the nuget feed