Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Using member 'BareMetalWeb.Core.DataScaffold.TryParseChildList(String, Type, out Object)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Child list parsing requires compiled entity types to be preserved.

'type' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicConstructors', 'DynamicallyAccessedMemberTypes.NonPublicConstructors' in call to 'System.Runtime.CompilerServices.RuntimeHelpers.GetUninitializedObject(Type)'. The parameter 'type' of method 'BareMetalWeb.Data.BinaryObjectSerializer.CreateInstance(Type)' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

Unrecognized value passed to the parameter 'typeName' of method 'System.Type.GetType(String, Boolean, Boolean)'. It's not possible to guarantee the availability of the target type.

Using member 'System.Reflection.Assembly.GetType(String, Boolean, Boolean)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Types might be removed by trimming. If the type name is a string literal, consider using Type.GetType instead.

Potential stack overflow. Move the stackalloc out of the loop. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2014)

'type' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicParameterlessConstructor' in call to 'BareMetalWeb.Data.BinaryObjectSerializer.CreateInstance(Type)'. The parameter 'type' of method 'BareMetalWeb.Data.BinaryObjectSerializer.ReadValue(ref SpanReader, Type, SchemaDefinition, Int32)' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'type' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicParameterlessConstructor' in call to 'BareMetalWeb.Data.BinaryObjectSerializer.CreateInstance(Type)'. The parameter 'type' of method 'BareMetalWeb.Data.BinaryObjectSerializer.ReadValue(BinaryReader, Type, SchemaDefinition, Int32)' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties' in call to 'System.Type.GetProperty(String)'. The field '(System.Type, System.String).Item1' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties' in call to 'System.Type.GetProperties(BindingFlags)'. The parameter 't' of method 'lambda expression' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

The field 'WalDirectIndex._disposed' is assigned but its value is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'childType' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties' in call to 'BareMetalWeb.Core.DataScaffold.BuildChildFieldMetadata(Type)'. The parameter 'type' of method 'lambda expression' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

Value passed to parameter 'childType' of method 'BareMetalWeb.Core.DataScaffold.IsChildListType(Type, out Type)' can not be statically determined and may not meet 'DynamicallyAccessedMembersAttribute' requirements.

'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties', 'DynamicallyAccessedMemberTypes.NonPublicProperties' in call to 'System.Type.GetProperty(String, BindingFlags)'. The field '(System.Type, System.String).Item1' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties', 'DynamicallyAccessedMemberTypes.NonPublicProperties' in call to 'System.Type.GetProperty(String, BindingFlags)'. The field '(System.Type, System.String).Item1' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'type' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicConstructors', 'DynamicallyAccessedMemberTypes.NonPublicConstructors' in call to 'System.Runtime.CompilerServices.RuntimeHelpers.GetUninitializedObject(Type)'. The parameter 'type' of method 'BareMetalWeb.Core.DataScaffold.IsDefaultValue(Object, Type)' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseDictionary(String, Type, out Object)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. Creating Dictionary<string,T> instances for value types requires dynamic code generation.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseDictionary(String, Type, out Object)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Dictionary parsing requires compiled entity types to be preserved.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseChildList(String, Type, out Object)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. Creating List<T> instances for child types requires dynamic code generation.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseChildList(String, Type, out Object)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Child list parsing requires compiled entity types to be preserved.

The field 'WalDirectIndex._disposed' is assigned but its value is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties', 'DynamicallyAccessedMemberTypes.NonPublicProperties' in call to 'System.Type.GetProperty(String, BindingFlags)'. The field '(System.Type, System.String).Item1' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties', 'DynamicallyAccessedMemberTypes.NonPublicProperties' in call to 'System.Type.GetProperty(String, BindingFlags)'. The field '(System.Type, System.String).Item1' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'type' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicConstructors', 'DynamicallyAccessedMemberTypes.NonPublicConstructors' in call to 'System.Runtime.CompilerServices.RuntimeHelpers.GetUninitializedObject(Type)'. The parameter 'type' of method 'BareMetalWeb.Core.DataScaffold.IsDefaultValue(Object, Type)' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties' in call to 'System.Type.GetProperty(String)'. The field '(System.Type, System.String).Item1' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseDictionary(String, Type, out Object)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. Creating Dictionary<string,T> instances for value types requires dynamic code generation.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseDictionary(String, Type, out Object)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Dictionary parsing requires compiled entity types to be preserved.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseChildList(String, Type, out Object)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. Creating List<T> instances for child types requires dynamic code generation.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseChildList(String, Type, out Object)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Child list parsing requires compiled entity types to be preserved.

'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties' in call to 'System.Type.GetProperties(BindingFlags)'. The parameter 't' of method 'lambda expression' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

The field 'WalDirectIndex._disposed' is assigned but its value is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Using member 'System.Reflection.Assembly.GetType(String, Boolean, Boolean)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Types might be removed by trimming. If the type name is a string literal, consider using Type.GetType instead.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseDictionary(String, Type, out Object)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. Creating Dictionary<string,T> instances for value types requires dynamic code generation.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseDictionary(String, Type, out Object)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Dictionary parsing requires compiled entity types to be preserved.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseChildList(String, Type, out Object)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. Creating List<T> instances for child types requires dynamic code generation.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseChildList(String, Type, out Object)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Child list parsing requires compiled entity types to be preserved.

Potential stack overflow. Move the stackalloc out of the loop. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2014)

'type' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicParameterlessConstructor' in call to 'BareMetalWeb.Data.BinaryObjectSerializer.CreateInstance(Type)'. The parameter 'type' of method 'BareMetalWeb.Data.BinaryObjectSerializer.ReadValue(ref SpanReader, Type, SchemaDefinition, Int32)' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'type' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicParameterlessConstructor' in call to 'BareMetalWeb.Data.BinaryObjectSerializer.CreateInstance(Type)'. The parameter 'type' of method 'BareMetalWeb.Data.BinaryObjectSerializer.ReadValue(BinaryReader, Type, SchemaDefinition, Int32)' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties' in call to 'System.Type.GetProperties(BindingFlags)'. The parameter 't' of method 'lambda expression' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

The field 'WalDirectIndex._disposed' is assigned but its value is never used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, azure/login@v2, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties', 'DynamicallyAccessedMemberTypes.NonPublicProperties' in call to 'System.Type.GetProperty(String, BindingFlags)'. The field '(System.Type, System.String).Item1' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties', 'DynamicallyAccessedMemberTypes.NonPublicProperties' in call to 'System.Type.GetProperty(String, BindingFlags)'. The field '(System.Type, System.String).Item1' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

'childType' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicProperties' in call to 'BareMetalWeb.Core.DataScaffold.BuildChildFieldMetadata(Type)'. The parameter 'type' of method 'lambda expression' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

Value passed to parameter 'childType' of method 'BareMetalWeb.Core.DataScaffold.IsChildListType(Type, out Type)' can not be statically determined and may not meet 'DynamicallyAccessedMembersAttribute' requirements.

'type' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicConstructors', 'DynamicallyAccessedMemberTypes.NonPublicConstructors' in call to 'System.Runtime.CompilerServices.RuntimeHelpers.GetUninitializedObject(Type)'. The parameter 'type' of method 'BareMetalWeb.Core.DataScaffold.IsDefaultValue(Object, Type)' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseDictionary(String, Type, out Object)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. Creating Dictionary<string,T> instances for value types requires dynamic code generation.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseDictionary(String, Type, out Object)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Dictionary parsing requires compiled entity types to be preserved.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseChildList(String, Type, out Object)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. Creating List<T> instances for child types requires dynamic code generation.

Using member 'BareMetalWeb.Core.DataScaffold.TryParseChildList(String, Type, out Object)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. Child list parsing requires compiled entity types to be preserved.

The field 'WalDirectIndex._disposed' is assigned but its value is never used