Serilog.Settings.Configuration 8.0.0

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
There is a newer prerelease version of this package available.
See the version list below for details.
dotnet add package Serilog.Settings.Configuration --version 8.0.0
NuGet\Install-Package Serilog.Settings.Configuration -Version 8.0.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Serilog.Settings.Configuration" Version="8.0.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Serilog.Settings.Configuration --version 8.0.0
#r "nuget: Serilog.Settings.Configuration, 8.0.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Serilog.Settings.Configuration as a Cake Addin
#addin nuget:?package=Serilog.Settings.Configuration&version=8.0.0

// Install Serilog.Settings.Configuration as a Cake Tool
#tool nuget:?package=Serilog.Settings.Configuration&version=8.0.0

Serilog.Settings.Configuration Build status NuGet Version

A Serilog settings provider that reads from Microsoft.Extensions.Configuration sources, including .NET Core's appsettings.json file.

By default, configuration is read from the Serilog section.

{
  "Serilog": {
    "Using":  [ "Serilog.Sinks.Console", "Serilog.Sinks.File" ],
    "MinimumLevel": "Debug",
    "WriteTo": [
      { "Name": "Console" },
      { "Name": "File", "Args": { "path": "Logs/log.txt" } }
    ],
    "Enrich": [ "FromLogContext", "WithMachineName", "WithThreadId" ],
    "Destructure": [
      { "Name": "With", "Args": { "policy": "Sample.CustomPolicy, Sample" } },
      { "Name": "ToMaximumDepth", "Args": { "maximumDestructuringDepth": 4 } },
      { "Name": "ToMaximumStringLength", "Args": { "maximumStringLength": 100 } },
      { "Name": "ToMaximumCollectionCount", "Args": { "maximumCollectionCount": 10 } }
    ],
    "Properties": {
        "Application": "Sample"
    }
  }
}

After installing this package, use ReadFrom.Configuration() and pass an IConfiguration object.

static void Main(string[] args)
{
    var configuration = new ConfigurationBuilder()
        .SetBasePath(Directory.GetCurrentDirectory())
        .AddJsonFile("appsettings.json")
        .AddJsonFile($"appsettings.{Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT") ?? "Production"}.json", true)
        .Build();

    var logger = new LoggerConfiguration()
        .ReadFrom.Configuration(configuration)
        .CreateLogger();

    logger.Information("Hello, world!");
}

This example relies on the Microsoft.Extensions.Configuration.Json, Serilog.Sinks.Console, Serilog.Sinks.File, Serilog.Enrichers.Environment and Serilog.Enrichers.Thread packages also being installed.

For a more sophisticated example go to the sample folder.

Syntax description

Root section name

Root section name can be changed:

{
  "CustomSection": {
    ...
  }
}
var options = new ConfigurationReaderOptions { SectionName = "CustomSection" };
var logger = new LoggerConfiguration()
    .ReadFrom.Configuration(configuration, options)
    .CreateLogger();

Using section and auto-discovery of configuration assemblies

Using section contains list of assemblies in which configuration methods (WriteTo.File(), Enrich.WithThreadId()) reside.

"Serilog": {
    "Using":  [ "Serilog.Sinks.Console", "Serilog.Enrichers.Thread", /* ... */ ],
    // ...
}

For .NET Core projects build tools produce .deps.json files and this package implements a convention using Microsoft.Extensions.DependencyModel to find any package among dependencies with Serilog anywhere in the name and pulls configuration methods from it, so the Using section in example above can be omitted:

{
  "Serilog": {
    "MinimumLevel": "Debug",
    "WriteTo": [ "Console" ],
    ...
  }
}

In order to utilize this convention for .NET Framework projects which are built with .NET Core CLI tools specify PreserveCompilationContext to true in the csproj properties:

<PropertyGroup Condition=" '$(TargetFramework)' == 'net46' ">
  <PreserveCompilationContext>true</PreserveCompilationContext>
</PropertyGroup>

In case of non-standard dependency management you can pass a custom DependencyContext object:

var functionDependencyContext = DependencyContext.Load(typeof(Startup).Assembly);

var options = new ConfigurationReaderOptions(functionDependencyContext) { SectionName = "AzureFunctionsJobHost:Serilog" };
var logger = new LoggerConfiguration()
    .ReadFrom.Configuration(hostConfig, options)
    .CreateLogger();

Alternatively, you can also pass an array of configuration assemblies:

var configurationAssemblies = new[]
{
    typeof(ConsoleLoggerConfigurationExtensions).Assembly,
    typeof(FileLoggerConfigurationExtensions).Assembly,
};
var options = new ConfigurationReaderOptions(configurationAssemblies);
var logger = new LoggerConfiguration()
    .ReadFrom.Configuration(configuration, options)
    .CreateLogger();

For legacy .NET Framework projects it also scans default probing path(s).

For all other cases, as well as in the case of non-conventional configuration assembly names DO use Using section.

.NET 5.0 onwards Single File Applications

Currently, auto-discovery of configuration assemblies is not supported in bundled mode. DO use Using section or explicitly pass a collection of configuration assemblies for workaround.

MinimumLevel, LevelSwitches, overrides and dynamic reload

The MinimumLevel configuration property can be set to a single value as in the sample above, or, levels can be overridden per logging source.

This is useful in ASP.NET Core applications, which will often specify minimum level as:

"MinimumLevel": {
    "Default": "Information",
    "Override": {
        "Microsoft": "Warning",
        "System": "Warning"
    }
}

MinimumLevel section also respects dynamic reload if the underlying provider supports it.

var configuration = new ConfigurationBuilder()
    .SetBasePath(Directory.GetCurrentDirectory())
    .AddJsonFile(path: "appsettings.json", reloadOnChange: true)
    .Build();

Any changes for Default, Microsoft, System sources will be applied at runtime.

(Note: only existing sources are respected for a dynamic update. Inserting new records in Override section is not supported.)

You can also declare LoggingLevelSwitch-es in custom section and reference them for sink parameters:

{
    "Serilog": {
        "LevelSwitches": { "controlSwitch": "Verbose" },
        "WriteTo": [
            {
                "Name": "Seq",
                "Args": {
                    "serverUrl": "http://localhost:5341",
                    "apiKey": "yeEZyL3SMcxEKUijBjN",
                    "controlLevelSwitch": "$controlSwitch"
                }
            }
        ]
    }
}

Level updates to switches are also respected for a dynamic update.

Since version 7.0.0, both declared switches (i.e. Serilog:LevelSwitches section) and minimum level override switches (i.e. Serilog:MinimumLevel:Override section) are exposed through a callback on the reader options so that a reference can be kept:

var allSwitches = new Dictionary<string, LoggingLevelSwitch>();
var options = new ConfigurationReaderOptions
{
    OnLevelSwitchCreated = (switchName, levelSwitch) => allSwitches[switchName] = levelSwitch
};

var logger = new LoggerConfiguration()
    .ReadFrom.Configuration(configuration, options)
    .CreateLogger();

LoggingLevelSwitch controlSwitch = allSwitches["$controlSwitch"];

WriteTo, Enrich, AuditTo, Destructure sections

These sections support simplified syntax, for example the following is valid if no arguments are needed by the sinks:

"WriteTo": [ "Console", "DiagnosticTrace" ]

Or alternatively, the long-form ("Name": ...) syntax from the example above can be used when arguments need to be supplied.

By Microsoft.Extensions.Configuration.Json convention, array syntax implicitly defines index for each element in order to make unique paths for configuration keys. So the example above is equivalent to:

"WriteTo": {
    "0": "Console",
    "1": "DiagnosticTrace"
}

And

"WriteTo:0": "Console",
"WriteTo:1": "DiagnosticTrace"

(The result paths for the keys will be the same, i.e. Serilog:WriteTo:0 and Serilog:WriteTo:1)

When overriding settings with environment variables it becomes less convenient and fragile, so you can specify custom names:

"WriteTo": {
    "ConsoleSink": "Console",
    "DiagnosticTraceSink": { "Name": "DiagnosticTrace" }
}

Properties section

This section defines a static list of key-value pairs that will enrich log events.

Filter section

This section defines filters that will be applied to log events. It is especially useful in combination with Serilog.Expressions (or legacy Serilog.Filters.Expressions) package so you can write expression in text form:

"Filter": [{
  "Name": "ByIncludingOnly",
  "Args": {
      "expression": "Application = 'Sample'"
  }
}]

Using this package you can also declare LoggingFilterSwitch-es in custom section and reference them for filter parameters:

{
    "Serilog": {
        "FilterSwitches": { "filterSwitch": "Application = 'Sample'" },
        "Filter": [
            {
                "Name": "ControlledBy",
                "Args": {
                    "switch": "$filterSwitch"
                }
            }
        ]
}

Level updates to switches are also respected for a dynamic update.

Since version 7.0.0, filter switches are exposed through a callback on the reader options so that a reference can be kept:

var filterSwitches = new Dictionary<string, ILoggingFilterSwitch>();
var options = new ConfigurationReaderOptions
{
    OnFilterSwitchCreated = (switchName, filterSwitch) => filterSwitches[switchName] = filterSwitch
};

var logger = new LoggerConfiguration()
    .ReadFrom.Configuration(configuration, options)
    .CreateLogger();

ILoggingFilterSwitch filterSwitch = filterSwitches["filterSwitch"];

Nested configuration sections

Some Serilog packages require a reference to a logger configuration object. The sample program in this project illustrates this with the following entry configuring the Serilog.Sinks.Async package to wrap the Serilog.Sinks.File package. The configure parameter references the File sink configuration:

"WriteTo:Async": {
  "Name": "Async",
  "Args": {
    "configure": [
      {
        "Name": "File",
        "Args": {
          "path": "%TEMP%/Logs/serilog-configuration-sample.txt",
          "outputTemplate":
              "{Timestamp:o} [{Level:u3}] ({Application}/{MachineName}/{ThreadId}) {Message}{NewLine}{Exception}"
        }
      }
    ]
  }
},

Destructuring

Destructuring means extracting pieces of information from an object and create properties with values; Serilog offers the @ structure-capturing operator. In case there is a need to customize the way log events are serialized (e.g., hide property values or replace them with something else), one can define several destructuring policies, like this:

"Destructure": [
  {
    "Name": "With",
    "Args": {
      "policy": "MyFirstNamespace.FirstDestructuringPolicy, MyFirstAssembly"
    }
  },
  {
    "Name": "With",
    "Args": {
      "policy": "policy": "MySecondNamespace.SecondDestructuringPolicy, MySecondAssembly"
    }
  },
   {
    "Name": "With",
    "Args": {
      "policy": "policy": "MyThirdNamespace.ThirdDestructuringPolicy, MyThirdAssembly"
    }
  },
],

This is how the first destructuring policy would look like:

namespace MyFirstNamespace;

public record MyDto(int Id, int Name);

public class FirstDestructuringPolicy : IDestructuringPolicy
{
    public bool TryDestructure(object value, ILogEventPropertyValueFactory propertyValueFactory, 
        [NotNullWhen(true)] out LogEventPropertyValue? result)
    {
        if (value is not MyDto dto)
        {
            result = null;
            return false;
        }

        result = new StructureValue(new List<LogEventProperty>
        {
            new LogEventProperty("Identifier", new ScalarValue(deleteTodoItemInfo.Id)),
            new LogEventProperty("NormalizedName", new ScalarValue(dto.Name.ToUpperInvariant()))
        });

        return true;
    }
}

Assuming Serilog needs to destructure an argument of type MyDto when handling a log event:

logger.Information("About to process input: {@MyDto} ...", myDto);

it will apply FirstDestructuringPolicy which will convert MyDto instance to a StructureValue instance; a Serilog console sink would write the following entry:

About to process input: {"Identifier": 191, "NormalizedName": "SOME_UPPER_CASE_NAME"} ...

Arguments binding

When the configuration specifies a discrete value for a parameter (such as a string literal), the package will attempt to convert that value to the target method's declared CLR type of the parameter. Additional explicit handling is provided for parsing strings to Uri, TimeSpan, enum, arrays and custom collections.

Since version 7.0.0, conversion will use the invariant culture (CultureInfo.InvariantCulture) as long as the ReadFrom.Configuration(IConfiguration configuration, ConfigurationReaderOptions options) method is used. Obsolete methods use the current culture to preserve backward compatibility.

Static member support

Static member access can be used for passing to the configuration argument via special syntax:

{
  "Args": {
     "encoding": "System.Text.Encoding::UTF8",
     "theme": "Serilog.Sinks.SystemConsole.Themes.AnsiConsoleTheme::Code, Serilog.Sinks.Console"
  }
}

Complex parameter value binding

If the parameter value is not a discrete value, it will try to find a best matching public constructor for the argument:

{
  "Name": "Console",
  "Args": {
    "formatter": {
      // `type` (or $type) is optional, must be specified for abstract declared parameter types
      "type": "Serilog.Templates.ExpressionTemplate, Serilog.Expressions",
      "template": "[{@t:HH:mm:ss} {@l:u3} {Coalesce(SourceContext, '<none>')}] {@m}\n{@x}"
      }
  }
}

For other cases the package will use the configuration binding system provided by Microsoft.Extensions.Options.ConfigurationExtensions to attempt to populate the parameter. Almost anything that can be bound by IConfiguration.Get<T> should work with this package. An example of this is the optional List<Column> parameter used to configure the .NET Standard version of the Serilog.Sinks.MSSqlServer package.

Abstract parameter types

If parameter type is an interface or an abstract class you need to specify the full type name that implements abstract type. The implementation type should have parameterless constructor.

"Destructure": [
    { "Name": "With", "Args": { "policy": "Sample.CustomPolicy, Sample" } },
    ...
],

IConfiguration parameter

If a Serilog package requires additional external configuration information (for example, access to a ConnectionStrings section, which would be outside of the Serilog section), the sink should include an IConfiguration parameter in the configuration extension method. This package will automatically populate that parameter. It should not be declared in the argument list in the configuration source.

IConfigurationSection parameters

Certain Serilog packages may require configuration information that can't be easily represented by discrete values or direct binding-friendly representations. An example might be lists of values to remove from a collection of default values. In this case the method can accept an entire IConfigurationSection as a call parameter and this package will recognize that and populate the parameter. In this way, Serilog packages can support arbitrarily complex configuration scenarios.

Samples

Azure Functions (v2, v3)

hosts.json

{
  "version": "2.0",
  "logging": {
    "applicationInsights": {
      "samplingExcludedTypes": "Request",
      "samplingSettings": {
        "isEnabled": true
      }
    }
  },
  "Serilog": {
    "MinimumLevel": {
        "Default": "Information",
        "Override": {
            "Microsoft": "Warning",
            "System": "Warning"
        }
    },
    "Enrich": [ "FromLogContext" ],
    "WriteTo": [
      { "Name": "Seq", "Args": { "serverUrl": "http://localhost:5341" } }
    ]
  }
}

In Startup.cs section name should be prefixed with AzureFunctionsJobHost

public class Startup : FunctionsStartup
{
    public override void Configure(IFunctionsHostBuilder builder)
    {
        builder.Services.AddSingleton<ILoggerProvider>(sp =>
        {
            var functionDependencyContext = DependencyContext.Load(typeof(Startup).Assembly);

            var hostConfig = sp.GetRequiredService<IConfiguration>();
            var options = new ConfigurationReaderOptions(functionDependencyContext) { SectionName = "AzureFunctionsJobHost:Serilog" };
            var logger = new LoggerConfiguration()
                .ReadFrom.Configuration(hostConfig, options)
                .CreateLogger();

            return new SerilogLoggerProvider(logger, dispose: true);
        });
    }
}

In order to make auto-discovery of configuration assemblies work, modify Function's csproj file

<Project Sdk="Microsoft.NET.Sdk">

  

  
  <Target Name="FunctionsPostBuildDepsCopy" AfterTargets="PostBuildEvent">
    <Copy SourceFiles="$(OutDir)$(AssemblyName).deps.json" DestinationFiles="$(OutDir)bin\$(AssemblyName).deps.json" />
  </Target>

  <Target Name="FunctionsPublishDepsCopy" AfterTargets="Publish">
    <Copy SourceFiles="$(OutDir)$(AssemblyName).deps.json" DestinationFiles="$(PublishDir)bin\$(AssemblyName).deps.json" />
  </Target>

</Project>

Versioning

This package tracks the versioning and target framework support of its Microsoft.Extensions.Configuration dependency.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 is compatible.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (639)

Showing the top 5 NuGet packages that depend on Serilog.Settings.Configuration:

Package Downloads
Serilog.AspNetCore The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

Serilog support for ASP.NET Core logging

Umbraco.Cms.Infrastructure The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

Contains the infrastructure assembly needed to run Umbraco CMS.

IppDotNetSdkForQuickBooksApiV3

The IPP .NET SDK for QuickBooks V3 is a set of .NET classes that make it easier to call QuickBooks APIs. This is the .Net Standard 2.0 version of the .Net SDK

NET6CustomLibrary

open source custom dotnet extension library

Sitko.Core.App

Sitko.Core is a set of libraries to help build .NET Core applications fast

GitHub repositories (128)

Showing the top 5 popular GitHub repositories that depend on Serilog.Settings.Configuration:

Repository Stars
jellyfin/jellyfin
The Free Software Media System
microsoft/ailab
Experience, Learn and Code the latest breakthrough innovations with Microsoft AI
RayWangQvQ/BiliBiliToolPro
B 站(bilibili)自动任务工具,支持docker、青龙、k8s等多种部署方式。敏感肌也能用。
Kareadita/Kavita
Kavita is a fast, feature rich, cross platform reading server. Built with the goal of being a full solution for all your reading needs. Setup your own server and share your reading collection with your friends and family.
EventStore/EventStore
EventStoreDB, the event-native database. Designed for Event Sourcing, Event-Driven, and Microservices architectures
Version Downloads Last updated
8.0.1-dev-00582 5,624 3/21/2024
8.0.1-dev-00575 8,885 2/26/2024
8.0.1-dev-00572 5,838 2/19/2024
8.0.1-dev-00571 215 2/19/2024
8.0.1-dev-00561 73,154 11/15/2023
8.0.0 12,091,512 11/15/2023
8.0.0-dev-00556 435 11/15/2023
8.0.0-dev-00555 407 11/15/2023
8.0.0-dev-00550 583 11/13/2023
7.0.2-dev-00546 42,364 8/30/2023
7.0.1 4,970,222 8/23/2023
7.0.1-dev-00540 717 8/21/2023
7.0.0 20,367,182 5/10/2023
7.0.0-dev-00538 633 8/5/2023
7.0.0-dev-00535 641 7/5/2023
7.0.0-dev-00529 1,182 5/10/2023
7.0.0-dev-00527 1,233 5/9/2023
7.0.0-dev-00525 774 5/8/2023
7.0.0-dev-00521 628 5/8/2023
7.0.0-dev-00519 591 5/8/2023
7.0.0-dev-00513 940 5/5/2023
7.0.0-dev-00508 4,282 5/5/2023
7.0.0-dev-00504 641 5/5/2023
4.0.0-dev-00499 13,526 4/21/2023
4.0.0-dev-00486 26,208 3/21/2023
4.0.0-dev-00484 624 3/21/2023
4.0.0-dev-00482 692 3/21/2023
4.0.0-dev-00473 3,727 3/16/2023
4.0.0-dev-00456 13,402 3/15/2023
4.0.0-dev-00452 631 3/14/2023
4.0.0-dev-00448 1,822 3/13/2023
4.0.0-dev-00443 645 3/13/2023
4.0.0-dev-00440 1,008 3/12/2023
4.0.0-dev-00417 643 3/12/2023
4.0.0-dev-00413 631 3/12/2023
4.0.0-dev-00411 735 3/11/2023
4.0.0-dev-00408 630 3/11/2023
4.0.0-dev-00401 611 3/11/2023
4.0.0-dev-00395 627 3/10/2023
4.0.0-dev-00389 836 3/10/2023
4.0.0-dev-00385 805 3/9/2023
3.5.0-dev-00383 6,269 3/9/2023
3.5.0-dev-00370 113,799 1/6/2023
3.5.0-dev-00367 17,651 12/19/2022
3.5.0-dev-00359 115,086 10/18/2022
3.5.0-dev-00357 4,085 10/13/2022
3.5.0-dev-00355 22,848 9/14/2022
3.5.0-dev-00353 730 9/13/2022
3.5.0-dev-00352 767 9/13/2022
3.4.0 30,529,402 9/13/2022
3.3.1-dev-00337 160,694 5/13/2022
3.3.1-dev-00335 781 5/12/2022
3.3.1-dev-00327 1,319 5/11/2022
3.3.1-dev-00323 708 5/11/2022
3.3.1-dev-00313 14,911 4/14/2022
3.3.1-dev-00296 134,372 1/8/2022
3.3.0 112,122,312 10/7/2021
3.3.0-dev-00291 145,610 8/31/2021
3.2.1-dev-00288 25,538 8/13/2021
3.2.0 7,183,821 8/11/2021
3.2.0-dev-00283 788 8/11/2021
3.2.0-dev-00281 727 8/11/2021
3.2.0-dev-00272 99,195 5/7/2021
3.2.0-dev-00269 3,602 5/3/2021
3.2.0-dev-00266 34,371 3/26/2021
3.2.0-dev-00264 167,018 11/24/2020
3.2.0-dev-00261 1,618 11/23/2020
3.2.0-dev-00257 1,857 11/20/2020
3.2.0-dev-00249 30,871 11/6/2020
3.2.0-dev-00244 459,156 5/26/2020
3.2.0-dev-00239 14,498 5/13/2020
3.1.1-dev-00237 13,468 5/13/2020
3.1.1-dev-00234 1,708 5/12/2020
3.1.1-dev-00232 1,326 5/11/2020
3.1.1-dev-00228 1,391 5/10/2020
3.1.1-dev-00224 65,577 3/25/2020
3.1.1-dev-00216 879,404 11/21/2019
3.1.1-dev-00209 460,779 6/3/2019
3.1.0 168,533,689 6/2/2019
3.1.0-dev-00206 1,225 6/2/2019
3.1.0-dev-00204 1,208 6/2/2019
3.1.0-dev-00202 1,176 6/2/2019
3.1.0-dev-00200 1,183 6/2/2019
3.0.2-dev-00198 3,240 5/24/2019
3.0.2-dev-00195 14,932 5/6/2019
3.0.2-dev-00187 90,877 1/7/2019
3.0.2-dev-00186 1,487 1/7/2019
3.0.2-dev-00185 1,301 1/7/2019
3.0.2-dev-00183 1,284 1/7/2019
3.0.2-dev-00171 1,469 1/4/2019
3.0.1 12,509,289 10/17/2018
3.0.1-dev-00163 1,620 10/17/2018
3.0.1-dev-00160 7,366 10/15/2018
3.0.0 670,220 10/7/2018
3.0.0-dev-00149 1,299 10/7/2018
3.0.0-dev-00147 1,311 10/7/2018
3.0.0-dev-00142 1,345 10/6/2018
3.0.0-dev-00139 1,334 10/5/2018
3.0.0-dev-00133 5,196 9/29/2018
3.0.0-dev-00128 3,297 9/22/2018
3.0.0-dev-00125 4,969 9/16/2018
3.0.0-dev-00119 35,997 7/28/2018
3.0.0-dev-00116 7,737 7/18/2018
3.0.0-dev-00113 12,106 7/9/2018
3.0.0-dev-00112 62,967 5/14/2018
3.0.0-dev-00111 2,461 5/9/2018
3.0.0-dev-00108 3,738 4/30/2018
3.0.0-dev-00103 2,656 4/21/2018
3.0.0-dev-00097 4,316 4/11/2018
3.0.0-dev-00093 13,542 4/5/2018
3.0.0-dev-00083 48,141 3/14/2018
2.6.1 9,823,164 3/15/2018
2.6.0 23,243 3/14/2018
2.6.0-dev-00081 9,074 2/13/2018
2.5.1-dev-00078 1,585 2/13/2018
2.5.0 918,428 2/10/2018
2.4.1-dev-00072 4,616 1/30/2018
2.4.1-dev-00070 21,872 12/15/2017
2.4.1-dev-00063 19,670 11/8/2017
2.4.1-dev-00061 28,286 9/7/2017
2.4.0 2,668,160 5/18/2017
2.4.0-dev-00057 6,081 4/12/2017
2.4.0-dev-00055 2,017 4/5/2017
2.3.2-dev-00054 1,553 4/5/2017
2.3.1 113,199 4/5/2017
2.3.1-dev-00049 1,578 4/5/2017
2.3.0 16,190 3/29/2017
2.3.0-dev-00044 4,137 3/10/2017
2.3.0-dev-00042 5,244 1/17/2017
2.2.1-dev-00041 1,541 1/17/2017
2.2.0 280,726 11/6/2016
2.2.0-dev-00035 6,948 9/1/2016
2.1.0 51,592 7/26/2016
2.1.0-dev-00028 2,385 7/6/2016
2.1.0-dev-00026 1,670 7/5/2016
2.0.0 63,024 7/5/2016
2.0.0-rc-8 2,074 5/27/2016
2.0.0-rc-21 1,727 6/20/2016
2.0.0-rc-19 1,631 6/6/2016
2.0.0-rc-17 1,524 6/4/2016
2.0.0-rc-15 1,554 6/1/2016
2.0.0-rc-13 1,591 5/27/2016
2.0.0-beta-6 2,797 3/9/2016
2.0.0-beta-5 1,611 3/4/2016
2.0.0-beta-4 1,639 3/4/2016