chore(deps): update dependency node to v22 - workflows - .github/workflows/e2e.yml #8722
ci.yml
on: pull_request
Matrix: build-ubuntu
build-windows
4m 8s
build result
4s
Annotations
12 errors and 10 warnings
|
build-ubuntu (24.x, 8.0)
Process completed with exit code 1.
|
|
test/ConfigLoader.test.ts > ConfigLoader > loadRemoteConfig > should throw error if config file is not valid JSON:
test/ConfigLoader.test.ts#L632
AssertionError: expected [Function] to throw error matching /Invalid configuration format in git/ but got 'Failed to pull repository: Command fa…'
- Expected:
/Invalid configuration format in git/
+ Received:
"Failed to pull repository: Command failed: git pull
You are not currently on a branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.
git pull <remote> <branch>
"
❯ timeout test/ConfigLoader.test.ts:632:9
|
|
test/ConfigLoader.test.ts > ConfigLoader > loadRemoteConfig > should throw error if config path was not found:
test/ConfigLoader.test.ts#L614
AssertionError: expected [Function] to throw error matching /Configuration file not found at/ but got 'Failed to pull repository: Command fa…'
- Expected:
/Configuration file not found at/
+ Received:
"Failed to pull repository: Command failed: git pull
You are not currently on a branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.
git pull <remote> <branch>
"
❯ timeout test/ConfigLoader.test.ts:614:9
|
|
test/ConfigLoader.test.ts > ConfigLoader > loadRemoteConfig > should throw error if repository is a valid git repo but the branch does not exist:
test/ConfigLoader.test.ts#L596
AssertionError: expected [Function] to throw error matching /Failed to checkout branch/ but got 'Failed to pull repository: Command fa…'
- Expected:
/Failed to checkout branch/
+ Received:
"Failed to pull repository: Command failed: git pull
You are not currently on a branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.
git pull <remote> <branch>
"
❯ timeout test/ConfigLoader.test.ts:596:9
|
|
test/ConfigLoader.test.ts > ConfigLoader > loadRemoteConfig > should throw error for invalid configuration file path (git):
test/ConfigLoader.test.ts#L483
AssertionError: expected [Function] to throw error including 'Invalid configuration file path in re…' but got 'Failed to pull repository: Command fa…'
- Expected
+ Received
- Invalid configuration file path in repository
+ Failed to pull repository: Command failed: git pull
+ From https://github.com/finos/git-proxy
+ * [new branch] 1384-fix-cancel-api-base -> origin/1384-fix-cancel-api-base
+ * [new branch] 1386-remote-folder-cleanup -> origin/1386-remote-folder-cleanup
+ * [new branch] 1388-reduce-db-bloat -> origin/1388-reduce-db-bloat
+ * [new branch] approved-licenses-list-ui -> origin/approved-licenses-list-ui
+ * [new branch] li_updates -> origin/li_updates
+ * [new branch] main -> origin/main
+ * [new branch] make-auth-config-schema-more-intuitive -> origin/make-auth-config-schema-more-intuitive
+ * [new branch] renovate/major-22-dockerfile -> origin/renovate/major-22-dockerfile
+ * [new branch] renovate/major-24-dockerfile -> origin/renovate/major-24-dockerfile
+ * [new branch] renovate/major-24-npm -> origin/renovate/major-24-npm
+ * [new branch] renovate/major-4-npm -> origin/renovate/major-4-npm
+ * [new branch] renovate/major-7-npm -> origin/renovate/major-7-npm
+ * [new branch] renovate/major-8-docker-compose -> origin/renovate/major-8-docker-compose
+ * [new branch] renovate/manager -> origin/renovate/manager
+ * [new branch] renovate/website-manager -> origin/renovate/website-manager
+ * [new branch] renovate/workflows-major-22-github-actions -> origin/renovate/workflows-major-22-github-actions
+ * [new branch] renovate/workflows-major-24-github-actions -> origin/renovate/workflows-major-24-github-actions
+ * [new branch] test/e2e-wf-change -> origin/test/e2e-wf-change
+ * [new tag] license-inventory-0.0.1 -> license-inventory-0.0.1
+ * [new tag] license-inventory-0.0.2 -> license-inventory-0.0.2
+ * [new tag] sample-0.1.0 -> sample-0.1.0
+ * [new tag] sample-0.1.1 -> sample-0.1.1
+ * [new tag] v1.0.0 -> v1.0.0
+ * [new tag] v1.1.0 -> v1.1.0
+ * [new tag] v1.10.0 -> v1.10.0
+ * [new tag] v1.11.0 -> v1.11.0
+ * [new tag] v1.12.0 -> v1.12.0
+ * [new tag] v1.13.0 -> v1.13.0
+ * [new tag] v1.14.0 -> v1.14.0
+ * [new tag] v1.15.0 -> v1.15.0
+ * [new tag] v1.16.0 -> v1.16.0
+ * [new tag] v1.17.0 -> v1.17.0
+ * [new tag] v1.17.1 -> v1.17.1
+ * [new tag] v1.17.2 -> v1.17.2
+ * [new tag] v1.18.0 -> v1.18.0
+ * [new tag] v1.18.1 -> v1.18.1
+ * [new tag] v1.18.2 -> v1.18.2
+ * [new tag] v1.19.0 -> v1.19.0
+ * [new tag] v1.19.1 -> v1.19.1
+ * [new tag] v1.19.2 -> v1.19.2
+ * [new tag] v1.2.0 -> v1.2.0
+ * [new tag] v1.2.1 -> v1.2.1
+ * [new tag] v1.2.2 -> v1.2.2
+ * [new tag] v1.2.3 -> v1.2.3
+ * [new tag] v1.3.0 -> v1.3.0
+ * [new tag] v1.3.1 -> v1.3.1
+ * [new tag] v1.3.10 -> v1.3.10
+ * [new tag] v1.3.2 -> v1.3.2
+ * [new tag] v1.3.3 -> v1.3.3
+ * [new tag] v1.3.4 -> v1.3.4
+ * [new tag] v1.3.5 -> v1.3.5
+ * [new tag] v1.3.6 -> v1.3.6
+ * [new tag] v1.3.7 -> v1.3.7
+ * [new tag] v1.3.8 -> v1.3.8
+ * [new tag] v1.3.9 -> v1.3.9
+ * [new tag]
|
|
test/ConfigLoader.test.ts > ConfigLoader > loadRemoteConfig > should load configuration from git repository:
test/ConfigLoader.test.ts#L458
Error: Test timed out in 10000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/ConfigLoader.test.ts:458:5
|
|
build-ubuntu (24.x, 6.0)
Process completed with exit code 1.
|
|
test/ConfigLoader.test.ts > ConfigLoader > loadRemoteConfig > should throw error for invalid configuration file path (git):
test/ConfigLoader.test.ts#L474
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".
❯ test/ConfigLoader.test.ts:474:5
|
|
test/ConfigLoader.test.ts > ConfigLoader > loadRemoteConfig > should load configuration from git repository:
test/ConfigLoader.test.ts#L458
Error: Test timed out in 10000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/ConfigLoader.test.ts:458:5
|
|
build-ubuntu (20.x, 7.0)
Process completed with exit code 1.
|
|
test/ConfigLoader.test.ts > ConfigLoader > loadRemoteConfig > should load configuration from git repository:
test/ConfigLoader.test.ts#L458
Error: Test timed out in 10000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/ConfigLoader.test.ts:458:5
|
|
build result
Process completed with exit code 1.
|
|
build-ubuntu (24.x, 8.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-ubuntu (24.x, 6.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-ubuntu (24.x, 7.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-ubuntu (20.x, 7.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-ubuntu (22.x, 8.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-ubuntu (20.x, 8.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-ubuntu (20.x, 6.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-ubuntu (22.x, 7.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-ubuntu (22.x, 6.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-ubuntu-node-20.x-mongo-6.0
|
1.88 MB |
sha256:a774fb40dfac36c4e947d48c0339c148128962c52436a4d712921c3eeff020ca
|
|
|
build-ubuntu-node-20.x-mongo-8.0
|
1.88 MB |
sha256:a3f87325b421e49f93f6c8cb371d3cda5937a3387220b6a8e448419fc30103a8
|
|
|
build-ubuntu-node-22.x-mongo-6.0
|
1.88 MB |
sha256:cbbdb50f8cd0481667604765c46ff9f9aed6af526c94cb37cd6eb85074c67591
|
|
|
build-ubuntu-node-22.x-mongo-7.0
|
1.88 MB |
sha256:5538f2e6a615a27d19f0def127bd279e650f65b870f4c517386d1d482ecf5359
|
|
|
build-ubuntu-node-22.x-mongo-8.0
|
1.88 MB |
sha256:cbc990b1a981e8200b172a1cf137fa31a766c1a0d8157ea82db1186837fe56ab
|
|
|
build-ubuntu-node-24.x-mongo-7.0
|
1.88 MB |
sha256:b9c7e9020779fa2f6ae23b06a6f80bf8c6ccdb08e7d184f2877612edaf7a71c4
|
|