v10.1.0

One call answers differently, on the .NET 11 runtime only: Changed answers in 10.1.0.

Changed answers

• Literals: a time, DateTime or DateTimeOffset element with an hour of 24 throws FormatException on the .NET 11 runtime too, where it returned midnight: {24:00:00} read as {00:00:00} and T24:00:00 as the next day. On .NET 10 it always threw (#300, Migration).

Fixed

• Value sets: ToString on every value set, in the core and NodaTime packages, runs in a net11.0 Native AOT consumer, where the process ended with SIGTRAP on the first call (Native AOT).
• EF Core: Any or Count over an empty captured list of ranges or value sets returns false or 0 on EF Core 10.0.2 and later, where it failed with 42883: operator does not exist: text && int4range. The stopgap AppContext.SetSwitch("Microsoft.EntityFrameworkCore.Issue37216", true) also brings back EF Core's own failure on empty lists of other types (EF Core).
• EF Core: RangeSet.Contains translates on the EF Core 10 patch that carries dotnet/efcore#37081, where every overload threw ArgumentException inside EF Core before translation. That patch, planned as 10.0.15, was not published when 10.1.0 shipped. Its stopgap AppContext.SetSwitch("Microsoft.EntityFrameworkCore.Issue37081", true) also gives up EF Core's own fix for IReadOnlySet parameters, which inline their values again (EF Core).
• EF Core: ExecuteUpdate of a value set inside a JSON column is refused naming the property ('Doc.Tags') on Npgsql EF 10.0.3 with SetPostgresVersion(16, 0) or higher, where it was refused naming the column ('Doc'), and the refusal no longer says that a value that may be null writes NULL as the whole document (EF Core).
• EF Core: a == b ? null : a over a value set Union computed on the server, which EF Core writes as NULLIF(a, b), is refused as value set equality, where it was refused naming no operation (EF Core).

Published to nuget.org through Trusted Publishing by this run. The CycloneDX SBOM for each package is attached below.