Nuget / SemVer. How can I increase my version number when adding a new dependency, but not change the public API?

Question

I manage the library using SemVer and redirect it using NuGet.

I am making some corrections and performance-related changes that do not change the public library API in any way, but include adding a new dependency.

Usually I just increase the patch or lower versions when fixing or changing the private code. Is this possible when adding a new dependency? Or should I increase the main version, despite the absence of changes in the public API? Are there any specific recommendations on such issues?

Answer 1

You should almost certainly use a minor version change.

The Wikipedia article on version numbers reads:

In principle, in subsequent releases, the main number increases when there are significant transitions in functionality, the minor number increases when only minor functions or significant corrections are added, and the version number increases with minor errors.

I would consider addiction as secondary. In addition, performance is a secondary feature unless it is a significant limitation that users face and you are making a significant improvement.