fix(deps): update dependency log-symbols to v7 - abandoned #18415
ardatanmain.yml
on: pull_request
Linting Check
/
eslint
1m 33s
🧹 Prettier Check
2m 32s
Testing exports integrity
1m 32s
Examples - Normal
6m 17s
Matrix: Validating dev-tests
Matrix: test-watcher
Matrix: test
Annotations
23 errors and 13 warnings
|
Unit Test on Node (windows-latest) and GraphQL v16
Process completed with exit code 1.
|
|
tests/init.spec.ts > init > custom setup:
packages/graphql-codegen-cli/tests/init.spec.ts#L359
Error: Snapshot `init > custom setup 1` mismatched
- Expected
+ Received
@@ -2,11 +2,11 @@
import type { CodegenConfig } from '@graphql-codegen/cli';
const config: CodegenConfig = {
overwrite: true,
schema: "http://localhost:4000",
- documents: "graphql/*.ts",
+ documents: "src/**/*.tsx",
generates: {
"src/gql/": {
preset: "client",
plugins: []
},
❯ tests/init.spec.ts:359:20
|
|
tests/init.spec.ts > init > should have few default values for React:
packages/graphql-codegen-cli/tests/init.spec.ts#L326
AssertionError: expected 'graphql-codegen --config codegen.ts' to deeply equal 'graphql-codegen --config app-codegen.…'
Expected: "graphql-codegen --config app-codegen.yml"
Received: "graphql-codegen --config codegen.ts"
❯ tests/init.spec.ts:326:41
|
|
tests/init.spec.ts > init > plugins suggestions non client-side setup > should use typescript related plugins when typescript is found (node):
packages/graphql-codegen-cli/tests/init.spec.ts#L235
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/init.spec.ts:235:5
|
|
tests/init.spec.ts > init > plugins suggestions for client-side setup > should use stencil related plugins when @stencil/core is found:
packages/graphql-codegen-cli/tests/init.spec.ts#L199
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/init.spec.ts:199:5
|
|
tests/init.spec.ts > init > plugins suggestions for client-side setup > should use react related plugins when react is found:
packages/graphql-codegen-cli/tests/init.spec.ts#L167
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/init.spec.ts:167:5
|
|
tests/init.spec.ts > init > plugins suggestions for client-side setup > should use angular related plugins when @angular/core is found:
packages/graphql-codegen-cli/tests/init.spec.ts#L134
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/init.spec.ts:134:5
|
|
Unit Test on Node 20 (ubuntu-latest) and GraphQL v15
The strategy configuration was canceled because "test.windows-latest_16_20" failed
|
|
Unit Test on Node 24 (ubuntu-latest) and GraphQL v15
The strategy configuration was canceled because "test.windows-latest_16_20" failed
|
|
Unit Test on Node 22 (ubuntu-latest) and GraphQL v16
The strategy configuration was canceled because "test.windows-latest_16_20" failed
|
|
Unit Test on Node 22 (ubuntu-latest) and GraphQL v16
The operation was canceled.
|
|
Unit Test on Node 20 (ubuntu-latest) and GraphQL v16
The strategy configuration was canceled because "test.windows-latest_16_20" failed
|
|
Unit Test on Node 20 (ubuntu-latest) and GraphQL v16
The operation was canceled.
|
|
Unit Test on Node 24 (ubuntu-latest) and GraphQL v16
The strategy configuration was canceled because "test.windows-latest_16_20" failed
|
|
Unit Test on Node 24 (ubuntu-latest) and GraphQL v16
The operation was canceled.
|
|
tests/init.spec.ts > init > custom setup:
packages/graphql-codegen-cli/tests/init.spec.ts#L332
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/init.spec.ts:332:3
|
|
tests/init.spec.ts > init > should have few default values for React:
packages/graphql-codegen-cli/tests/init.spec.ts#L328
Error: Snapshot `init > should have few default values for React 1` mismatched
- Expected
+ Received
@@ -3,9 +3,6 @@
documents: "graphql/**/*.graphql"
generates:
graphql/index.ts:
preset: "client"
plugins: []
- ./graphql.schema.json:
- plugins:
- - "introspection"
"
❯ tests/init.spec.ts:328:20
|
|
tests/init.spec.ts > init > should have few default values for Angular:
packages/graphql-codegen-cli/tests/init.spec.ts#L268
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/init.spec.ts:268:3
|
|
tests/init.spec.ts > init > plugins suggestions for client-side setup > should use stencil related plugins when @stencil/core is found:
packages/graphql-codegen-cli/tests/init.spec.ts#L199
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/init.spec.ts:199:5
|
|
tests/init.spec.ts > init > plugins suggestions for client-side setup > should use react related plugins when react is found:
packages/graphql-codegen-cli/tests/init.spec.ts#L167
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/init.spec.ts:167:5
|
|
tests/init.spec.ts > init > plugins suggestions for client-side setup > should use angular related plugins when @angular/core is found:
packages/graphql-codegen-cli/tests/init.spec.ts#L134
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/init.spec.ts:134:5
|
|
Unit Test on Node 22 (ubuntu-latest) and GraphQL v15
The strategy configuration was canceled because "test.windows-latest_16_20" failed
|
|
Unit Test on Node 22 (ubuntu-latest) and GraphQL v15
The operation was canceled.
|
|
🧹 Prettier Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Linting Check / eslint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Validating dev-tests (esm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Testing exports integrity
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Validating dev-tests (cjs)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Watcher Unit Test on Node 20 (ubuntu-latest) and GraphQL v16
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Unit Test on Node (windows-latest) and GraphQL v16
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Unit Test on Node 20 (ubuntu-latest) and GraphQL v16
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Unit Test on Node 24 (ubuntu-latest) and GraphQL v16
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Unit Test on Node 22 (ubuntu-latest) and GraphQL v15
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Examples - Normal
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Watcher Unit Test on Node 20 (ubuntu-latest) and GraphQL v15
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
Watcher Unit Test on Node (windows-latest) and GraphQL v16
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|