Skip to content

Rename projects to Nimblesite.* namespace, remove Gatekeeper and Samples #90

Rename projects to Nimblesite.* namespace, remove Gatekeeper and Samples

Rename projects to Nimblesite.* namespace, remove Gatekeeper and Samples #90

Triggered via pull request April 4, 2026 02:33
Status Failure
Total duration 5m 22s
Artifacts

ci.yml

on: pull_request
Lint + DataProvider Tests
37s
Lint + DataProvider Tests
Build + LQL / Migration / Sync Tests
5m 18s
Build + LQL / Migration / Sync Tests
LQL Extension Tests
14s
LQL Extension Tests
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 7 warnings
LQL Extension Tests
Process completed with exit code 1.
Lint + DataProvider Tests
Process completed with exit code 2.
Build + LQL / Migration / Sync Tests
Process completed with exit code 1.
LQL Extension Tests
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 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/
Lint + DataProvider Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, actions/setup-node@v4, actions/upload-artifact@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/
Lint + DataProvider Tests
No files were found with the provided path: **/TestResults/*.trx. No artifacts will be uploaded.
Build + LQL / Migration / Sync Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@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/
Build + LQL / Migration / Sync Tests
No files were found with the provided path: **/TestResults/*.trx. No artifacts will be uploaded.
Build + LQL / Migration / Sync Tests: Lql/Nimblesite.Lql.TypeProvider.FSharp.Tests/TypeProviderE2ETests.fs#L97
Nullness warning: A non-nullable 'obj' was expected but this expression is nullable. Consider either changing the target to also be nullable, or use pattern matching to safely handle the null case of this expression.
Build + LQL / Migration / Sync Tests: Lql/Nimblesite.Lql.TypeProvider.FSharp.Tests/TypeProviderE2ETests.fs#L97
Nullness warning: A non-nullable 'obj' was expected but this expression is nullable. Consider either changing the target to also be nullable, or use pattern matching to safely handle the null case of this expression.