Process completed with exit code 1.

The type or namespace name 'PrivateCatalogOptions' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'PrivateCatalogOptions' could not be found (are you missing a using directive or an assembly reference?)

Process completed with exit code 1.

The type or namespace name 'PrivateCatalogOptions' could not be found (are you missing a using directive or an assembly reference?)

The type or namespace name 'PrivateCatalogOptions' could not be found (are you missing a using directive or an assembly reference?)

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/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)

Method RejectMillisecondJwt passes 'options' as the paramName argument to a ArgumentException constructor. Replace this argument with one of the method's parameter names. Note that the provided parameter name should have the exact casing as declared on the method. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2208)

Ambiguous reference in cref attribute: 'AddCatalogAsync'. Assuming 'Microsoft.AI.Foundry.Local.ICatalog.AddCatalogAsync(string, System.Collections.Generic.Dictionary<string, string>?, System.Threading.CancellationToken?)', but could have also matched other overloads including 'Microsoft.AI.Foundry.Local.ICatalog.AddCatalogAsync(string, Microsoft.AI.Foundry.Local.PrivateCatalogOptions, System.Threading.CancellationToken?)'.

Parameter 'ct' has no matching param tag in the XML comment for 'ICatalog.AddCatalogAsync(string, Dictionary<string, string>?, CancellationToken?)' (but other parameters do)

Parameter 'name' has no matching param tag in the XML comment for 'ICatalog.AddCatalogAsync(string, Dictionary<string, string>?, CancellationToken?)' (but other parameters do)

Ambiguous reference in cref attribute: 'AddCatalogAsync'. Assuming 'Microsoft.AI.Foundry.Local.ICatalog.AddCatalogAsync(string, System.Collections.Generic.Dictionary<string, string>?, System.Threading.CancellationToken?)', but could have also matched other overloads including 'Microsoft.AI.Foundry.Local.ICatalog.AddCatalogAsync(string, Microsoft.AI.Foundry.Local.PrivateCatalogOptions, System.Threading.CancellationToken?)'.

Parameter 'ct' has no matching param tag in the XML comment for 'ICatalog.AddCatalogAsync(string, Dictionary<string, string>?, CancellationToken?)' (but other parameters do)

Parameter 'name' has no matching param tag in the XML comment for 'ICatalog.AddCatalogAsync(string, Dictionary<string, string>?, CancellationToken?)' (but other parameters do)

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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Parameter 'ct' has no matching param tag in the XML comment for 'ICatalog.AddCatalogAsync(string, Dictionary<string, string>?, CancellationToken?)' (but other parameters do)

Parameter 'name' has no matching param tag in the XML comment for 'ICatalog.AddCatalogAsync(string, Dictionary<string, string>?, CancellationToken?)' (but other parameters do)

Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)

Method RejectMillisecondJwt passes 'options' as the paramName argument to a ArgumentException constructor. Replace this argument with one of the method's parameter names. Note that the provided parameter name should have the exact casing as declared on the method. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2208)

Ambiguous reference in cref attribute: 'AddCatalogAsync'. Assuming 'Microsoft.AI.Foundry.Local.ICatalog.AddCatalogAsync(string, System.Collections.Generic.Dictionary<string, string>?, System.Threading.CancellationToken?)', but could have also matched other overloads including 'Microsoft.AI.Foundry.Local.ICatalog.AddCatalogAsync(string, Microsoft.AI.Foundry.Local.PrivateCatalogOptions, System.Threading.CancellationToken?)'.

Parameter 'ct' has no matching param tag in the XML comment for 'ICatalog.AddCatalogAsync(string, Dictionary<string, string>?, CancellationToken?)' (but other parameters do)

Parameter 'name' has no matching param tag in the XML comment for 'ICatalog.AddCatalogAsync(string, Dictionary<string, string>?, CancellationToken?)' (but other parameters do)

Ambiguous reference in cref attribute: 'AddCatalogAsync'. Assuming 'Microsoft.AI.Foundry.Local.ICatalog.AddCatalogAsync(string, System.Collections.Generic.Dictionary<string, string>?, System.Threading.CancellationToken?)', but could have also matched other overloads including 'Microsoft.AI.Foundry.Local.ICatalog.AddCatalogAsync(string, Microsoft.AI.Foundry.Local.PrivateCatalogOptions, System.Threading.CancellationToken?)'.

Parameter 'ct' has no matching param tag in the XML comment for 'ICatalog.AddCatalogAsync(string, Dictionary<string, string>?, CancellationToken?)' (but other parameters do)

Parameter 'name' has no matching param tag in the XML comment for 'ICatalog.AddCatalogAsync(string, Dictionary<string, string>?, CancellationToken?)' (but other parameters do)

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/setup-node@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/setup-node@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026