Skip to content

Release/v3.0.0

Release/v3.0.0 #13

Triggered via pull request March 30, 2026 20:29
Status Failure
Total duration 2m 50s
Artifacts 1

PullRequest-CI.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 24 warnings
Release to Nuget
😭 project file not found
Run-Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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-Test
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-dotnet@v3, actions/upload-artifact@v4, gittools/actions/gitversion/execute@v0.9.7, gittools/actions/gitversion/setup@v0.9.7. 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-Test: src/DataFuse.Adapters.Abstraction/CollectionResult.cs#L9
Missing XML comment for publicly visible type or member 'CollectionResult<T>.CollectionResult()'
Build-Test: src/DataFuse.Adapters.Abstraction/CollectionResult.cs#L5
Missing XML comment for publicly visible type or member 'CollectionResult<T>.CollectionResult(IEnumerable<T>)'
Build-Test: src/DataFuse.Adapters.Abstraction/CollectionResult.cs#L3
Missing XML comment for publicly visible type or member 'CollectionResult<T>'
Build-Test: src/DataFuse.Adapters.Abstraction/ChildrenQueries.cs#L6
Missing XML comment for publicly visible type or member 'ChildrenQueries.Queries'
Build-Test: src/DataFuse.Adapters.Abstraction/ChildrenQueries.cs#L5
Missing XML comment for publicly visible type or member 'ChildrenQueries.ParentQueryResultType'
Build-Test: src/DataFuse.Adapters.Abstraction/ChildrenQueries.cs#L3
Missing XML comment for publicly visible type or member 'ChildrenQueries'
Build-Test: src/DataFuse.Adapters.Abstraction/CacheResultAttribute.cs#L3
Missing XML comment for publicly visible type or member 'CacheResultAttribute'
Build-Test: src/DataFuse.Adapters.Abstraction/BaseTransformer.cs#L3
Missing XML comment for publicly visible type or member 'BaseTransformer<TQueryResult, TEntity>'
Build-Test: src/DataFuse.Adapters.Abstraction/QueryList.cs#L50
The member 'QueryList.Count()' does not hide an accessible member. The new keyword is not required.
Build-Test: src/DataFuse.Adapters.Abstraction/EntityConfiguration.cs#L17
XML comment has badly formed XML -- 'Whitespace is not allowed at this location.'
Build-Test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build-Test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build-Test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build-Test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build-Test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build-Test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build-Test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build-Test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build-Test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build-Test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-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/
Release to Nuget
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, Rebel028/publish-nuget@v2.8.0. 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/

Artifacts

Produced during runtime
Name Size Digest
build-artifact Expired
207 MB
sha256:7c324279bd7257e306aaf8b8a40b63e3a25909ebc84fecf747d5e486876609d9