When updating to a new major version of .NET (in this case from .NET 5 to .NET 6) without needing to make any change other than selecting the new target framework in Visual Studio, does this warrant a new major version or does bumping the minor version suffice, when adhering to SemVer-principles?

When I updated from .NET Framework 4.8 to .NET 5, that was a reason to bump the major number imo, as there were a lot of changes made internally, but for the above case I'm not sure.

My app is a local executable for end users, I have no API people will have to rely on. I know it's not that important under those circumstances, but I'm new to developing and want to learn it the "right" way from the start.

When updating to a new major version of .NET (in this case from .NET 5 to .NET 6) without needing to make any change other than selecting the new target framework in Visual Studio, does this warrant a new major or minor version or does bumping the patch version suffice, when adhering to SemVer-principles?

When I updated from .NET Framework 4.8 to .NET 5, that was a reason to bump the major number imo, as there were a lot of changes made internally, but for the above case I'm not sure.

My app is a local executable for end users, I have no API people will have to rely on. I know it's not that important under those circumstances, but I'm still new to developing and want to learn it the "right" way from the start.

When updating to a new major version of .NET (in this case from .NET 5 to .NET 6) without needing to make any change other than selecting the new target framework in Visual Studio, does this warrant a new major version or does bumping the minor version suffice, when adhering to SemVer-principles?

When I updated from .NET Framework 4.8 to .NET 5, that was a reason to bump the major number imo, as there were a lot of changes made internally, but for the above case I'm not sure.

When updating to a new major version of .NET (in this case from .NET 5 to .NET 6) without needing to make any change other than selecting the new target framework in Visual Studio, does this warrant a new major version or does bumping the minor version suffice, when adhering to SemVer-principles?

When I updated from .NET Framework 4.8 to .NET 5, that was a reason to bump the major number imo, as there were a lot of changes made internally, but for the above case I'm not sure.

My app is a local executable for end users, I have no API people will have to rely on. I know it's not that important under those circumstances, but I'm new to developing and want to learn it the "right" way from the start.

When updating to a new major version of .NET (in this case from .NET 5 to .NET 6) without needing to make any change other than selecting the new target framework in Visual Studio, does this warrant a new major version or does bumping the minor version suffice, when adhering to SemVer-principles?

When I updated from .NET Framework 4.8 to .NET 5, that was clearly a reason to bump the major number, as there were a lot of changes made internally, but for the above case I'm not sure.

When updating to a new major version of .NET (in this case from .NET 5 to .NET 6) without needing to make any change other than selecting the new target framework in Visual Studio, does this warrant a new major version or does bumping the minor version suffice, when adhering to SemVer-principles?

When I updated from .NET Framework 4.8 to .NET 5, that was a reason to bump the major number imo, as there were a lot of changes made internally, but for the above case I'm not sure.