chore(deps): bump ci-info from 3.7.1 to 4.1.0 #133
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
3m 34s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
4m 1s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
4m 16s
TypeScript Compatibility
3m 28s
Typecheck Examples and Tests
2m 52s
Lint
43s
Validate Yarn dependencies and constraints
17s
Node LTS on Ubuntu with leak detection
52s
Matrix: test-coverage
Matrix: test-ubuntu / test-jasmine
Matrix: test-ubuntu / test
Matrix: test-macos / test-jasmine
Matrix: test-macos / test
Matrix: test-windows / test-jasmine
Matrix: test-windows / test
Annotations
61 errors and 72 warnings
Lint
Process completed with exit code 1.
|
Node LTS on Ubuntu with leak detection
Process completed with exit code 1.
|
the jsdom console is the same as the test console:
e2e/__tests__/console.test.ts#L92
expect(received).toMatchSnapshot()
Snapshot name: `the jsdom console is the same as the test console 2`
- Snapshot - 0
+ Received + 2
+ (node:4756) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
PASS __tests__/console.test.js
✓ can mock console.error calls from jsdom
at Object.toMatchSnapshot (e2e/__tests__/console.test.ts:92:16)
|
test-ubuntu / Node LTS on ubuntu-latest using jest-jasmine2 (4/4)
Process completed with exit code 1.
|
on node >=16.12.0 › supports import assertions:
e2e/__tests__/nativeEsm.test.ts#L122
expect(received).toMatchSnapshot()
Snapshot name: `on node >=16.12.0 supports import assertions 1`
- Snapshot - 2
+ Received + 2
- Test Suites: 1 passed, 1 total
+ Test Suites: 1 failed, 1 total
- Tests: 2 passed, 2 total
+ Tests: 0 total
Snapshots: 0 total
Time: <<REPLACED>>
Ran all test suites matching /native-esm-import-assertions.test/i.
at Object.toMatchSnapshot (e2e/__tests__/nativeEsm.test.ts:122:21)
|
should work without error:
e2e/__tests__/domDiffing.test.ts#L16
expect(received).toMatchSnapshot()
Snapshot name: `should work without error 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/dom.test.js
+ "(node:6254) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/dom.test.js
✕ use toBe compare two div
✕ compare span and div
● use toBe compare two div
↵
at Object.toMatchSnapshot (e2e/__tests__/domDiffing.test.ts:16:16)
|
test-ubuntu / Node LTS on ubuntu-latest using jest-jasmine2 (3/4)
Process completed with exit code 1.
|
on node >=16.12.0 › supports import assertions:
e2e/__tests__/nativeEsm.test.ts#L124
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/nativeEsm.test.ts:124:22)
|
on node >=16.12.0 › supports import assertions:
e2e/__tests__/nativeEsm.test.ts#L122
expect(received).toMatchSnapshot()
Snapshot name: `on node >=16.12.0 supports import assertions 1`
- Snapshot - 2
+ Received + 2
- Test Suites: 1 passed, 1 total
+ Test Suites: 1 failed, 1 total
- Tests: 2 passed, 2 total
+ Tests: 0 total
Snapshots: 0 total
Time: <<REPLACED>>
Ran all test suites matching /native-esm-import-assertions.test/i.
at Object.toMatchSnapshot (e2e/__tests__/nativeEsm.test.ts:122:21)
|
should work without error:
e2e/__tests__/domDiffing.test.ts#L16
expect(received).toMatchSnapshot()
Snapshot name: `should work without error 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/dom.test.js
+ "(node:6574) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/dom.test.js
✕ use toBe compare two div
✕ compare span and div
● use toBe compare two div
↵
at Object.toMatchSnapshot (e2e/__tests__/domDiffing.test.ts:16:16)
|
Node LTS on Ubuntu with coverage (3/4)
Process completed with exit code 1.
|
the jsdom console is the same as the test console:
e2e/__tests__/console.test.ts#L92
expect(received).toMatchSnapshot()
Snapshot name: `the jsdom console is the same as the test console 2`
- Snapshot - 0
+ Received + 2
+ (node:4504) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
PASS __tests__/console.test.js
✓ can mock console.error calls from jsdom
at Object.toMatchSnapshot (e2e/__tests__/console.test.ts:92:16)
|
Node LTS on Ubuntu with coverage (4/4)
Process completed with exit code 1.
|
Wrong globals for environment › print useful error for navigator:
e2e/__tests__/wrongEnv.test.ts#L13
expect(received).toBe(expected) // Object.is equality
Expected: 1
Received: 0
at toBe (e2e/__tests__/wrongEnv.test.ts:13:27)
at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:27:5)
|
Wrong globals for environment › print useful error for unref:
e2e/__tests__/wrongEnv.test.ts#L14
expect(received).toMatchSnapshot()
Snapshot name: `Wrong globals for environment print useful error for unref 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/jsdom.js
+ "(node:6270) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/jsdom.js
✕ use unref
● use unref
The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string.
at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:14:46)
at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:31:5)
|
Node LTS on Ubuntu with coverage (2/4)
Process completed with exit code 1.
|
Wrong globals for environment › print useful error for navigator:
e2e/__tests__/wrongEnv.test.ts#L13
expect(received).toBe(expected) // Object.is equality
Expected: 1
Received: 0
at toBe (e2e/__tests__/wrongEnv.test.ts:13:27)
at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:27:5)
|
Wrong globals for environment › print useful error for unref:
e2e/__tests__/wrongEnv.test.ts#L14
expect(received).toMatchSnapshot()
Snapshot name: `Wrong globals for environment print useful error for unref 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/jsdom.js
+ "(node:6330) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/jsdom.js
✕ use unref
● use unref
The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string.
at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:14:46)
at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:31:5)
|
test-ubuntu / Node LTS on ubuntu-latest using jest-jasmine2 (2/4)
Process completed with exit code 1.
|
print correct error message with nested test definitions outside describe:
e2e/__tests__/nestedTestDefinitions.test.ts#L29
expect(received).toMatchSnapshot()
Snapshot name: `print correct error message with nested test definitions outside describe 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/nestedTestOutsideDescribe.js
+ "(node:3827) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/nestedTestOutsideDescribe.js
✕ outer test
● outer test
Tests cannot be nested. Test "inner test" cannot run because it is nested within "outer test".
at Object.toMatchSnapshot (e2e/__tests__/nestedTestDefinitions.test.ts:29:44)
|
print correct error message with nested test definitions inside describe:
e2e/__tests__/nestedTestDefinitions.test.ts#L39
expect(received).toMatchSnapshot()
Snapshot name: `print correct error message with nested test definitions inside describe 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/nestedTestWithinDescribe.js
+ "(node:4002) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/nestedTestWithinDescribe.js
in describe
✕ outer test
● in describe › outer test
↵
at Object.toMatchSnapshot (e2e/__tests__/nestedTestDefinitions.test.ts:39:44)
|
Node LTS on Ubuntu with coverage (1/4)
Process completed with exit code 1.
|
print correct error message with nested test definitions outside describe:
e2e/__tests__/nestedTestDefinitions.test.ts#L29
expect(received).toMatchSnapshot()
Snapshot name: `print correct error message with nested test definitions outside describe 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/nestedTestOutsideDescribe.js
+ "(node:3699) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/nestedTestOutsideDescribe.js
✕ outer test
● outer test
Tests cannot be nested. Test "inner test" cannot run because it is nested within "outer test".
at Object.toMatchSnapshot (e2e/__tests__/nestedTestDefinitions.test.ts:29:44)
|
print correct error message with nested test definitions inside describe:
e2e/__tests__/nestedTestDefinitions.test.ts#L39
expect(received).toMatchSnapshot()
Snapshot name: `print correct error message with nested test definitions inside describe 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/nestedTestWithinDescribe.js
+ "(node:3841) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/nestedTestWithinDescribe.js
in describe
✕ outer test
● in describe › outer test
↵
at Object.toMatchSnapshot (e2e/__tests__/nestedTestDefinitions.test.ts:39:44)
|
test-ubuntu / Node LTS on ubuntu-latest using jest-jasmine2 (1/4)
Process completed with exit code 1.
|
test-macos / Node v14.x on macos-latest (3/4)
Unable to find Node version '14.x' for platform darwin and architecture arm64.
|
test-macos / Node v14.x on macos-latest (1/4)
Unable to find Node version '14.x' for platform darwin and architecture arm64.
|
test-macos / Node v14.x on macos-latest (2/4)
Unable to find Node version '14.x' for platform darwin and architecture arm64.
|
TypeScript Compatibility:
node_modules/@tsconfig/node14/tsconfig.json#L7
Argument for '--module' option must be: 'none', 'commonjs', 'amd', 'system', 'umd', 'es6', 'es2015', 'es2020', 'esnext'.
|
TypeScript Compatibility:
node_modules/@tsconfig/node14/tsconfig.json#L13
Argument for '--moduleResolution' option must be: 'node', 'classic'.
|
TypeScript Compatibility
Import assignment cannot be used when targeting ECMAScript modules. Consider using 'import * as ns from "mod"', 'import {a} from "mod"', 'import d from "mod"', or another module format instead.
|
TypeScript Compatibility
Process completed with exit code 1.
|
print correct error message with nested test definitions outside describe:
e2e/__tests__/nestedTestDefinitions.test.ts#L29
expect(received).toMatchSnapshot()
Snapshot name: `print correct error message with nested test definitions outside describe 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/nestedTestOutsideDescribe.js
+ "(node:6185) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/nestedTestOutsideDescribe.js
✕ outer test
● outer test
Tests cannot be nested. Test "inner test" cannot run because it is nested within "outer test".
at Object.toMatchSnapshot (e2e/__tests__/nestedTestDefinitions.test.ts:29:44)
|
print correct error message with nested test definitions inside describe:
e2e/__tests__/nestedTestDefinitions.test.ts#L39
expect(received).toMatchSnapshot()
Snapshot name: `print correct error message with nested test definitions inside describe 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/nestedTestWithinDescribe.js
+ "(node:6345) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/nestedTestWithinDescribe.js
in describe
✕ outer test
● in describe › outer test
↵
at Object.toMatchSnapshot (e2e/__tests__/nestedTestDefinitions.test.ts:39:44)
|
test-macos / Node LTS on macos-latest using jest-jasmine2 (1/4)
Process completed with exit code 1.
|
test-macos / Node v14.x on macos-latest (4/4)
Unable to find Node version '14.x' for platform darwin and architecture arm64.
|
on node >=16.12.0 › supports import assertions:
e2e/__tests__/nativeEsm.test.ts#L122
expect(received).toMatchSnapshot()
Snapshot name: `on node >=16.12.0 supports import assertions 1`
- Snapshot - 2
+ Received + 2
- Test Suites: 1 passed, 1 total
+ Test Suites: 1 failed, 1 total
- Tests: 2 passed, 2 total
+ Tests: 0 total
Snapshots: 0 total
Time: <<REPLACED>>
Ran all test suites matching /native-esm-import-assertions.test/i.
at Object.toMatchSnapshot (e2e/__tests__/nativeEsm.test.ts:122:21)
|
should work without error:
e2e/__tests__/domDiffing.test.ts#L16
expect(received).toMatchSnapshot()
Snapshot name: `should work without error 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/dom.test.js
+ "(node:8399) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/dom.test.js
✕ use toBe compare two div
✕ compare span and div
● use toBe compare two div
↵
at Object.toMatchSnapshot (e2e/__tests__/domDiffing.test.ts:16:16)
|
test-macos / Node LTS on macos-latest using jest-jasmine2 (3/4)
Process completed with exit code 1.
|
the jsdom console is the same as the test console:
e2e/__tests__/console.test.ts#L92
expect(received).toMatchSnapshot()
Snapshot name: `the jsdom console is the same as the test console 2`
- Snapshot - 0
+ Received + 2
+ (node:11846) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
PASS __tests__/console.test.js
✓ can mock console.error calls from jsdom
at Object.toMatchSnapshot (e2e/__tests__/console.test.ts:92:16)
|
test-macos / Node LTS on macos-latest using jest-jasmine2 (4/4)
Process completed with exit code 1.
|
notify › does not report --notify flag:
e2e/__tests__/detectOpenHandles.ts#L111
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "Jest did not exit one second after the test run has completed.·
'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue."
at Object.toBe (e2e/__tests__/detectOpenHandles.ts:111:27)
|
Wrong globals for environment › print useful error for navigator:
e2e/__tests__/wrongEnv.test.ts#L13
expect(received).toBe(expected) // Object.is equality
Expected: 1
Received: 0
at toBe (e2e/__tests__/wrongEnv.test.ts:13:27)
at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:27:5)
|
Wrong globals for environment › print useful error for unref:
e2e/__tests__/wrongEnv.test.ts#L14
expect(received).toMatchSnapshot()
Snapshot name: `Wrong globals for environment print useful error for unref 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/jsdom.js
+ "(node:13812) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/jsdom.js
✕ use unref
● use unref
The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string.
at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:14:46)
at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:31:5)
|
test-macos / Node LTS on macos-latest using jest-jasmine2 (2/4)
Process completed with exit code 1.
|
the jsdom console is the same as the test console:
e2e/__tests__/console.test.ts#L92
expect(received).toMatchSnapshot()
Snapshot name: `the jsdom console is the same as the test console 2`
- Snapshot - 0
+ Received + 2
+ (node:4940) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
PASS __tests__/console.test.js
✓ can mock console.error calls from jsdom
at Object.toMatchSnapshot (e2e/__tests__/console.test.ts:92:16)
|
test-windows / Node LTS on windows-latest using jest-jasmine2 (4/4)
Process completed with exit code 1.
|
on node >=16.12.0 › supports import assertions:
e2e/__tests__/nativeEsm.test.ts#L122
expect(received).toMatchSnapshot()
Snapshot name: `on node >=16.12.0 supports import assertions 1`
- Snapshot - 2
+ Received + 2
- Test Suites: 1 passed, 1 total
+ Test Suites: 1 failed, 1 total
- Tests: 2 passed, 2 total
+ Tests: 0 total
Snapshots: 0 total
Time: <<REPLACED>>
Ran all test suites matching /native-esm-import-assertions.test/i.
at Object.toMatchSnapshot (e2e/__tests__/nativeEsm.test.ts:122:21)
|
should work without error:
e2e/__tests__/domDiffing.test.ts#L16
expect(received).toMatchSnapshot()
Snapshot name: `should work without error 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/dom.test.js
+ "(node:3748) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/dom.test.js
✕ use toBe compare two div
✕ compare span and div
● use toBe compare two div
↵
at Object.toMatchSnapshot (e2e/__tests__/domDiffing.test.ts:16:16)
|
test-windows / Node LTS on windows-latest using jest-jasmine2 (3/4)
Process completed with exit code 1.
|
print correct error message with nested test definitions outside describe:
e2e/__tests__/nestedTestDefinitions.test.ts#L29
expect(received).toMatchSnapshot()
Snapshot name: `print correct error message with nested test definitions outside describe 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/nestedTestOutsideDescribe.js
+ "(node:3556) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/nestedTestOutsideDescribe.js
✕ outer test
● outer test
Tests cannot be nested. Test "inner test" cannot run because it is nested within "outer test".
at Object.toMatchSnapshot (e2e/__tests__/nestedTestDefinitions.test.ts:29:44)
|
print correct error message with nested test definitions inside describe:
e2e/__tests__/nestedTestDefinitions.test.ts#L39
expect(received).toMatchSnapshot()
Snapshot name: `print correct error message with nested test definitions inside describe 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/nestedTestWithinDescribe.js
+ "(node:4068) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/nestedTestWithinDescribe.js
in describe
✕ outer test
● in describe › outer test
↵
at Object.toMatchSnapshot (e2e/__tests__/nestedTestDefinitions.test.ts:39:44)
|
outputs coverage report as json:
e2e/__tests__/coverageReport.test.ts#L102
expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
at Object.toBe (e2e/__tests__/coverageReport.test.ts:102:20)
|
test-windows / Node LTS on windows-latest using jest-jasmine2 (1/4)
Process completed with exit code 1.
|
Wrong globals for environment › print useful error for navigator:
e2e/__tests__/wrongEnv.test.ts#L13
expect(received).toBe(expected) // Object.is equality
Expected: 1
Received: 0
at toBe (e2e/__tests__/wrongEnv.test.ts:13:27)
at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:27:5)
|
Wrong globals for environment › print useful error for unref:
e2e/__tests__/wrongEnv.test.ts#L14
expect(received).toMatchSnapshot()
Snapshot name: `Wrong globals for environment print useful error for unref 1`
- Snapshot - 1
+ Received + 3
@@ -1,6 +1,8 @@
- "FAIL __tests__/jsdom.js
+ "(node:5736) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
+ (Use `node --trace-deprecation ...` to show where the warning was created)
+ FAIL __tests__/jsdom.js
✕ use unref
● use unref
The error below may be caused by using the wrong test environment, see https://jestjs.io/docs/configuration#testenvironment-string.
at toMatchSnapshot (e2e/__tests__/wrongEnv.test.ts:14:46)
at Object.assertFailuresAndSnapshot (e2e/__tests__/wrongEnv.test.ts:31:5)
|
test-windows / Node LTS on windows-latest using jest-jasmine2 (2/4)
Process completed with exit code 1.
|
can press "t" to filter by test name:
e2e/__tests__/watchModePatterns.test.ts#L70
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "t" to filter by test name: test results 1`
- Snapshot - 0
+ Received + 2
PASS __tests__/bar.spec.js
+ A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.
+
PASS __tests__/foo.spec.js
at toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:70:18)
at Array.forEach (<anonymous>)
at Object.forEach (e2e/__tests__/watchModePatterns.test.ts:69:11)
|
test-windows / Node v14.x on windows-latest (1/4)
Process completed with exit code 1.
|
Should throw if watchman used with haste.enableSymlinks:
e2e/Utils.ts#L156
EEXIST: file already exists, symlink 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test\symlinked-files\test.js' -> 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test\test-files\test.js'
at symlinkSync (e2e/Utils.ts:156:8)
at Array.forEach (<anonymous>)
at forEach (e2e/Utils.ts:149:25)
at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:30:16)
|
test-windows / Node v16.x on windows-latest (4/4)
Process completed with exit code 1.
|
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Validate Yarn dependencies and constraints
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Node LTS on Ubuntu with leak detection
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node LTS on ubuntu-latest using jest-jasmine2 (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node LTS on ubuntu-latest using jest-jasmine2 (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Node LTS on Ubuntu with coverage (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v14.x on ubuntu-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Node LTS on Ubuntu with coverage (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v14.x on ubuntu-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v14.x on ubuntu-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Node LTS on Ubuntu with coverage (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node LTS on ubuntu-latest using jest-jasmine2 (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Node LTS on Ubuntu with coverage (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node LTS on ubuntu-latest using jest-jasmine2 (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v14.x on ubuntu-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v16.x on ubuntu-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v16.x on ubuntu-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v14.x on macos-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Typecheck Examples and Tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v14.x on macos-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v16.x on ubuntu-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v18.x on ubuntu-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v16.x on ubuntu-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v14.x on macos-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
TypeScript Compatibility
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node LTS on macos-latest using jest-jasmine2 (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v14.x on macos-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node LTS on macos-latest using jest-jasmine2 (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v18.x on ubuntu-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v18.x on ubuntu-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v18.x on ubuntu-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node LTS on macos-latest using jest-jasmine2 (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node LTS on macos-latest using jest-jasmine2 (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v19.x on ubuntu-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v19.x on ubuntu-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v19.x on ubuntu-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-ubuntu / Node v19.x on ubuntu-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v16.x on macos-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node LTS on windows-latest using jest-jasmine2 (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node LTS on windows-latest using jest-jasmine2 (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node LTS on windows-latest using jest-jasmine2 (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v16.x on macos-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node LTS on windows-latest using jest-jasmine2 (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v14.x on windows-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v16.x on macos-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v14.x on windows-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v14.x on windows-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v16.x on macos-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v14.x on windows-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v18.x on macos-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v18.x on macos-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v16.x on windows-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v18.x on macos-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v16.x on windows-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v18.x on windows-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v16.x on windows-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v16.x on windows-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v18.x on macos-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v18.x on windows-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v18.x on windows-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v19.x on macos-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v18.x on windows-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v19.x on macos-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v19.x on windows-latest (1/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v19.x on macos-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v19.x on windows-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v19.x on windows-latest (2/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-windows / Node v19.x on windows-latest (3/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test-macos / Node v19.x on macos-latest (4/4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, SimenB/github-actions-cpu-cores@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|