Publish previews for .NET 11 #9715

Good news, you can use Scalar on .NET 11 today without waiting for a new release. Scalar.AspNetCore / Scalar.AspNetCore.Microsoft multi-target net9.0/net10.0, and a .NET 11 app resolves the net10.0 assets just fine thanks to roll-forward.

I verified this against .NET 11 Preview 6: a net11.0 minimal API using Microsoft.AspNetCore.OpenApi 11.0.0-preview.6 plus the latest Scalar.AspNetCore.Microsoft (2.16.18) restores with no warnings, and every Scalar transformer (x-codeSamples, x-badges, stability, ignore, …) runs correctly.

<PackageReference Include="Microsoft.AspNetCore.OpenApi" Version="11.0.0-preview.6.26359.118" />
<PackageReference Include="Scalar.AspNetCore.Microsoft" Version="2.16.18" />

using Scalar.AspNetCore;

var builder = WebApplication.CreateBuilder(args);
builder.Services.AddOpenApi(options => options.AddScalarTransformers());

var app = builder.Build();
app.MapOpenApi();
app.MapScalarApiReference();
app.Run();

We are holding off on adding a dedicated net11.0 target framework until .NET 11 reaches RC, so stable Scalar releases do not have to depend on preview packages. That mirrors how we added .NET 10 support during its RC/GA window, and the change itself is ready to flip on when the time comes.

One heads-up: .NET 11 emits OpenAPI 3.2 by default, and our 3.2 rendering support is still in progress. If you run into any rendering quirks, you can pin the document back to 3.1:

builder.Services.AddOpenApi(options =>
{
    options.OpenApiVersion = Microsoft.OpenApi.OpenApiSpecVersion.OpenApi3_1;
    options.AddScalarTransformers();
});

Hope that helps, let us know if anything does not work on 11!