Skip to content

Bump Microsoft.Data.Sqlite from 9.0.10 to 10.0.2 #246

Bump Microsoft.Data.Sqlite from 9.0.10 to 10.0.2

Bump Microsoft.Data.Sqlite from 9.0.10 to 10.0.2 #246

Triggered via pull request January 19, 2026 00:36
Status Success
Total duration 1m 59s
Artifacts

ci.yaml

on: pull_request
Matrix: Build
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
Build (ubuntu-latest): tests/IntegrationTests/BasicTests.cs#L46
Dereference of a possibly null reference.
Build (ubuntu-latest): src/Program.cs#L40
Using member 'Microsoft.AspNetCore.Http.Results.Json<TValue>(TValue, JsonSerializerOptions, String, Int32?)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext.
Build (ubuntu-latest): src/Program.cs#L40
Using member 'Microsoft.AspNetCore.Http.Results.Json<TValue>(TValue, JsonSerializerOptions, String, Int32?)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. JSON serialization and deserialization might require types that cannot be statically analyzed and might need runtime code generation. Use the overload that takes a JsonTypeInfo or JsonSerializerContext.
Build (ubuntu-latest): tests/IntegrationTests/BasicTests.cs#L46
Dereference of a possibly null reference.
Build (ubuntu-latest): src/Program.cs#L40
Using member 'Microsoft.AspNetCore.Http.Results.Json<TValue>(TValue, JsonSerializerOptions, String, Int32?)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext.
Build (ubuntu-latest): src/Program.cs#L40
Using member 'Microsoft.AspNetCore.Http.Results.Json<TValue>(TValue, JsonSerializerOptions, String, Int32?)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. JSON serialization and deserialization might require types that cannot be statically analyzed and might need runtime code generation. Use the overload that takes a JsonTypeInfo or JsonSerializerContext.
Build (windows-latest): tests/IntegrationTests/BasicTests.cs#L46
Dereference of a possibly null reference.
Build (windows-latest): src/Program.cs#L40
Using member 'Microsoft.AspNetCore.Http.Results.Json<TValue>(TValue, JsonSerializerOptions, String, Int32?)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext.
Build (windows-latest): src/Program.cs#L40
Using member 'Microsoft.AspNetCore.Http.Results.Json<TValue>(TValue, JsonSerializerOptions, String, Int32?)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. JSON serialization and deserialization might require types that cannot be statically analyzed and might need runtime code generation. Use the overload that takes a JsonTypeInfo or JsonSerializerContext.
Build (windows-latest): tests/IntegrationTests/BasicTests.cs#L46
Dereference of a possibly null reference.
Build (windows-latest): src/Program.cs#L40
Using member 'Microsoft.AspNetCore.Http.Results.Json<TValue>(TValue, JsonSerializerOptions, String, Int32?)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext.
Build (windows-latest): src/Program.cs#L40
Using member 'Microsoft.AspNetCore.Http.Results.Json<TValue>(TValue, JsonSerializerOptions, String, Int32?)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. JSON serialization and deserialization might require types that cannot be statically analyzed and might need runtime code generation. Use the overload that takes a JsonTypeInfo or JsonSerializerContext.