Can I jump from version 2.0.0 straight to 10.0.0 with SemVer?

November 18, 2026 3 answers
Asked by m.829+quexdaro

Our internal NuGet package is at 2.0.0, and we're moving it from .NET 8 to .NET 10. Can we jump the package version to 10.0.0 to match, while still following Semantic Versioning?

Answers

5z!wickerparcel_826

Yes. SemVer doesn't require major versions to increase one at a time, so 2.0.0 to 10.0.0 is allowed. The skipped numbers don't need to represent releases.

That said, a major version change tells consumers to look for incompatible changes. If the framework upgrade doesn't break your package's public API or compatibility for consumers, jumping the major just to match .NET can send a misleading signal.

m.829+quexdaro:

So the framework upgrade alone doesn't automatically determine the package's major version?

9u!bravdeli_248:

Right. Check what consumers have to change, including whether they can still use the package on the frameworks you previously supported.

Reply to this answer
Mivquelo-7t

I'd keep the package version separate from the .NET version and document compatibility in a small matrix. Matching them works neatly until your package has its own breaking change and needs another major release. Then a version like 11 could mean a package break, a .NET upgrade, or both.

A matrix also has room for other dependencies. A package version can't mirror all of them at once.

Reply to this answer
4s+socketwhisk_927

If matching .NET versions makes the package easier for your team to manage, you can choose that convention. Just write down what the numbers mean and how you'll handle package breaking changes between framework releases. Don't assume consumers will infer those rules from the version alone.

7d!velquari:

And if the numbering policy doesn't follow SemVer's rules, call it a different versioning convention rather than labeling it SemVer.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions