deps(nuget): Bump Microsoft.EntityFrameworkCore from 8.0.0 to 9.0.14 #805
ci-required.yml
on: pull_request
Matrix: API Integration / api-integration
Matrix: Backend Unit / backend-unit
Matrix: Frontend Unit / frontend-unit
Docs Governance
/
Docs Governance
9s
Backend Architecture
/
Backend Architecture
37s
Container Images
/
Container Images
32s
E2E Smoke
/
E2E Smoke
Annotations
9 errors and 9 warnings
|
API Integration / API Integration (ubuntu-latest)
Process completed with exit code 1.
|
|
API Integration / API Integration (ubuntu-latest):
backend/src/Taskdeck.Infrastructure/Repositories/KnowledgeChunkRepository.cs#L30
The call is ambiguous between the following methods or properties: 'Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ExecuteDeleteAsync<TSource>(System.Linq.IQueryable<TSource>, System.Threading.CancellationToken)' and 'Microsoft.EntityFrameworkCore.RelationalQueryableExtensions.ExecuteDeleteAsync<TSource>(System.Linq.IQueryable<TSource>, System.Threading.CancellationToken)'
|
|
Container Images / Container Images
Process completed with exit code 1.
|
|
Backend Unit / Backend Unit (ubuntu-latest)
Process completed with exit code 1.
|
|
Backend Unit / Backend Unit (ubuntu-latest):
backend/src/Taskdeck.Infrastructure/Repositories/KnowledgeChunkRepository.cs#L30
The call is ambiguous between the following methods or properties: 'Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ExecuteDeleteAsync<TSource>(System.Linq.IQueryable<TSource>, System.Threading.CancellationToken)' and 'Microsoft.EntityFrameworkCore.RelationalQueryableExtensions.ExecuteDeleteAsync<TSource>(System.Linq.IQueryable<TSource>, System.Threading.CancellationToken)'
|
|
API Integration / API Integration (windows-latest)
Process completed with exit code 1.
|
|
API Integration / API Integration (windows-latest):
backend/src/Taskdeck.Infrastructure/Repositories/KnowledgeChunkRepository.cs#L30
The call is ambiguous between the following methods or properties: 'Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ExecuteDeleteAsync<TSource>(System.Linq.IQueryable<TSource>, System.Threading.CancellationToken)' and 'Microsoft.EntityFrameworkCore.RelationalQueryableExtensions.ExecuteDeleteAsync<TSource>(System.Linq.IQueryable<TSource>, System.Threading.CancellationToken)'
|
|
Backend Unit / Backend Unit (windows-latest)
Process completed with exit code 1.
|
|
Backend Unit / Backend Unit (windows-latest):
backend/src/Taskdeck.Infrastructure/Repositories/KnowledgeChunkRepository.cs#L30
The call is ambiguous between the following methods or properties: 'Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ExecuteDeleteAsync<TSource>(System.Linq.IQueryable<TSource>, System.Threading.CancellationToken)' and 'Microsoft.EntityFrameworkCore.RelationalQueryableExtensions.ExecuteDeleteAsync<TSource>(System.Linq.IQueryable<TSource>, System.Threading.CancellationToken)'
|
|
Docs Governance / Docs Governance
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/
|
|
API Integration / API Integration (ubuntu-latest)
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@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/
|
|
Container Images / Container Images
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. 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/
|
|
Backend Architecture / Backend Architecture
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@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/
|
|
Backend Unit / Backend Unit (ubuntu-latest)
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@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/
|
|
API Integration / API Integration (windows-latest)
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@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/
|
|
Frontend Unit / Frontend Unit (ubuntu-latest)
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/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/
|
|
Backend Unit / Backend Unit (windows-latest)
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@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/
|
|
Frontend Unit / Frontend Unit (windows-latest)
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/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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
backend-unit-trx-ubuntu-latest
|
224 KB |
sha256:ff81d2aa1c26e11360897b1eb6951b799fad5a18b8af5b969732cd15d2ef91ec
|
|
|
backend-unit-trx-windows-latest
|
224 KB |
sha256:3499bb14054f5df3c4ce717b0ba4dcdb7f606de5b9970bf42a00e6b77c9d39e9
|
|
|
container-image-artifacts
|
894 Bytes |
sha256:0baf0433025fb47d60dada0145199e56d7587e8614525329605d497c1c568b6d
|
|
|
frontend-unit-artifacts-ubuntu-latest
|
831 KB |
sha256:236f5d27060094d8f61cf9cf3095439d698a8072870d7f657ea3210ddc0d272b
|
|
|
frontend-unit-artifacts-windows-latest
|
829 KB |
sha256:0253bfda764f705fe5202886ebdc956c750fccc197a973c0e1e73baac664005f
|
|