Versioning

Versioning in SkiaSharp is mostly simple, but is slightly different because it is based on the version of the underlying skia library version.

Stable Versions

As with all version numbers, there are 4 parts. However, these parts are not strictly the major.minor.build[.revision] that is typically associated with .NET versioning.

The version number for SkiaSharp is as follows: major.skia.minor.patch

• major represents a major upgrade that radically changes the underlying API and/or behavior
  This usually happens after a long period of using the same skia version and several iterations have finally made APIs obsolete. Or, it may be the case that there are fairly large behavior changes that might warrant some closer testing.
  An example would be when v2 changed the way color spaces were loaded and handled as well as the way text was processed.
• skia represents the milestone/tag provided by Google
  In many cases, this is not really a major change in the same way major because even though the engine has received many updates, the overall behavior is very similar. There are often some slight behavior changes, but not in such a way that will break existing apps/libraries.
• minor represents an update with either bug fixes or new APIs
  This is usually when a new feature is added or a bug is fixed. This is typically not a breaking change, and usually does not have behavior changes (except to fix the bug).
• patch represents a very minor change to either the assemblies or packaging
  This is not very common, but sometimes there is an issue that affects the usage of the library, but not the library itself. An example was with v1.68.1.1 when there was an issue with the assembly strong naming and it was only delay signed.

Preview Labels

With regards to the pre-release versioning, it follows the typical pattern. However, there is one type that is a bit different.

Although several preview versions are found on nuget.org, many more are also periodically released to the preview feed:
https://aka.ms/skiasharp-eap/index.json

Typically, the pre-release labels are:

• -alpha is very early and has not really been tested
• -preview is mostly good and works, but a few more things need to be done (bugs, features, discussions)
• -rc is almost ready to go out, but is waiting on third party feedback (not too common)

PR Packages

The exception to the pattern is the PR versions: -pr.xxxx.yy These builds are not on NuGet, but on the preview feed. These builds are directly related to a specific PR and contain either a bugfix or untested version of a feature.

These are used to release a feature for easy install, and will be soon merged into the main branch. Sometimes these builds are not as up-to-date as the main branch because they were forked. This is not always the case, and often are updated, but not always.