fix(ci): sync package-lock.json version 0.3.0 → 1.0.1 #18
xcodethinkAnnotations
21 errors and 9 warnings
|
Test (macos-14 · Node 18)
Process completed with exit code 1.
|
|
Test (windows-latest · Node 22)
Process completed with exit code 1.
|
|
tests/reporter.test.ts > writeHtmlReport — renderUnit details > renders the screenshot gallery when steps have a screenshot path:
tests/reporter.test.ts#L416
AssertionError: expected '<!doctype html>\n<html lang="en">\n<h…' to contain 'shots/01.png'
- Expected
+ Received
- shots/01.png
+ <!doctype html>
+ <html lang="en">
+ <head>
+ <meta charset="utf-8" />
+ <meta name="viewport" content="width=device-width,initial-scale=1" />
+ <title>demo-project — Audit run-x</title>
+ <style>
+ :root {
+ --bg: #0a0e14;
+ --bg-card: #11161d;
+ --bg-elevated: #1a212b;
+ --fg: #c9d1d9;
+ --fg-dim: #8b949e;
+ --border: #30363d;
+ --accent: #58a6ff;
+ --pass: #3fb950;
+ --warn: #d29922;
+ --fail: #f85149;
+ }
+ * { box-sizing: border-box; }
+ body {
+ margin: 0;
+ font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', system-ui, sans-serif;
+ background: var(--bg);
+ color: var(--fg);
+ line-height: 1.55;
+ }
+ header {
+ padding: 24px 32px;
+ border-bottom: 1px solid var(--border);
+ background: var(--bg-card);
+ }
+ header h1 {
+ margin: 0 0 6px;
+ font-size: 22px;
+ font-weight: 600;
+ }
+ header .meta {
+ color: var(--fg-dim);
+ font-size: 13px;
+ }
+ .container { max-width: 1200px; margin: 0 auto; padding: 24px 32px; }
+ .summary {
+ display: grid;
+ grid-template-columns: repeat(6, 1fr);
+ gap: 12px;
+ margin-bottom: 32px;
+ }
+ .summary .card {
+ background: var(--bg-card);
+ border: 1px solid var(--border);
+ border-radius: 8px;
+ padding: 16px;
+ text-align: center;
+ }
+ .summary .card .num {
+ font-size: 28px;
+ font-weight: 600;
+ margin-bottom: 4px;
+ }
+ .summary .card .label {
+ color: var(--fg-dim);
+ font-size: 12px;
+ text-transform: uppercase;
+ letter-spacing: 0.05em;
+ }
+ .unit {
+ background: var(--bg-card);
+ border: 1px solid var(--border);
+ border-radius: 8px;
+ padding: 20px 24px;
+ margin-bottom: 20px;
+ }
+ .unit h2 {
+ margin: 0 0 8px;
+ font-size: 17px;
+ display: flex;
+ align-items: center;
+ gap: 12px;
+ }
+ .badge {
+ display: inline-block;
+ padding: 2px 8px;
+ border-radius: 4px;
+ font-size: 11px;
+ font-weight: 600;
+ text-transform: uppercase;
+ letter-spacing: 0.05em;
+ }
+ .badge-pass { background: rgba(63, 185, 80, 0.15); color: var(--pass); }
+ .badge-warn { background: rgba(210, 153, 34, 0.15); color: var(--warn); }
+ .badge-fail { background: rgba(248, 81, 73, 0.15); color: var(--fail); }
+ .meta-row {
+ color: var(--fg-dim);
+ font-size: 12px;
+ margin-bottom: 16px;
+ }
+ .scores { display: flex; flex-wrap: wrap; gap: 8px; margin-bottom: 16px; }
+ .score-chip {
+ background: var(--bg-elevated);
+ padding: 6px 12px;
+ border-radius: 4px;
+ font-size: 12px;
+ }
+ .score-chip .v { font-weight: 600; color: var(--accent); }
+ .issues { margin-top: 12px; }
+ .issue {
+ padding: 10px 12px;
+ border-left: 3px solid var(--fail);
+ background: var(--bg-elevated);
+ border-radius: 0 4px 4px 0;
+ margin-bottom: 8px;
+ font-size: 13px;
+ }
+ .issue.high { border-color: var(--warn); }
+ .issue.medium { border-color: var(--accent); }
+ .issue.low { border-color: var(--fg-dim); }
+ .issue .rec {
+ color: var(--fg-dim);
+ margin-top: 4px;
+ font-size: 12px;
+ }
+ .steps {
+ margin-top: 16px;
+ background: var(--bg-elevated);
+ border-radius: 4px;
+ padding: 10px 14px;
+ }
+ .steps details summary {
+ cursor: pointer;
+ color: var(--fg-dim);
+ font-size: 12px;
+ user-select: none;
+ }
+ .step-list { list-style: none; padding: 0; margin: 10px 0 0; }
+ .step-list li {
+ padding: 4px 0;
+ font-size: 12px;
+ font-family: 'SF Mono', Consolas, monospace;
+ border-bottom: 1px solid var(--border);
+ }
+ .step-list li:last-child { border-bottom: none; }
+ .step-list li .st { display: inline-block; width: 50px; }
+ .gallery { display: grid; grid-template-columns: repeat(auto-fill, minmax(220px, 1fr)); gap: 12px; margin-top: 16px
|
|
tests/public-api-contract.test.ts > schema regeneration idempotence > each on-disk schema file matches a fresh JSON.parse + JSON.stringify of itself:
tests/public-api-contract.test.ts#L238
AssertionError: expected '{\r\n "$schema": "http://json-schema…' to be '{\n "$schema": "http://json-schema.o…' // Object.is equality
- Expected
+ Received
- {
+ {
- "$schema": "http://json-schema.org/draft-07/schema#",
+ "$schema": "http://json-schema.org/draft-07/schema#",
- "$id": "https://github.com/xcodethink/ai-browser-auditor/blob/main/docs/schemas/act-result.schema.json",
+ "$id": "https://github.com/xcodethink/ai-browser-auditor/blob/main/docs/schemas/act-result.schema.json",
- "title": "ActResult",
+ "title": "ActResult",
- "description": "MCP tool envelope returned by `act` (N-2 primitive). Per-step outcome of an action sequence (goto / click / fill / press / wait / wait_for / scroll / screenshot / act / note) plus a final DOM summary, console errors, and screenshot.",
+ "description": "MCP tool envelope returned by `act` (N-2 primitive). Per-step outcome of an action sequence (goto / click / fill / press / wait / wait_for / scroll / screenshot / act / note) plus a final DOM summary, console errors, and screenshot.",
- "x-result-schema-version": "1.2.0",
+ "x-result-schema-version": "1.2.0",
- "$ref": "#/definitions/ActResult",
+ "$ref": "#/definitions/ActResult",
- "definitions": {
+ "definitions": {
- "ActResult": {
+ "ActResult": {
- "type": "object",
+ "type": "object",
- "properties": {
+ "properties": {
- "schema_version": {
+ "schema_version": {
- "type": "string",
+ "type": "string",
- "pattern": "^\\d+\\.\\d+\\.\\d+$"
+ "pattern": "^\\d+\\.\\d+\\.\\d+$"
- },
+ },
- "url_input": {
+ "url_input": {
- "type": "string"
+ "type": "string"
- },
+ },
- "url_final": {
+ "url_final": {
- "type": "string"
+ "type": "string"
- },
+ },
- "title": {
+ "title": {
- "type": "string"
+ "type": "string"
- },
+ },
- "started_at": {
+ "started_at": {
- "type": "string"
+ "type": "string"
- },
+ },
- "finished_at": {
+ "finished_at": {
- "type": "string"
+ "type": "string"
- },
+ },
- "status": {
+ "status": {
- "type": "string",
+ "type": "string",
- "enum": [
+ "enum": [
- "ok",
+ "ok",
- "error"
+ "error"
- ]
+ ]
- },
+ },
- "error": {
+ "error": {
- "type": "string"
+ "type": "string"
- },
+ },
- "engine": {
+ "engine": {
- "type": "string",
+ "type": "string",
- "enum": [
+ "enum": [
- "playwright",
+ "playwright",
- "stagehand"
+ "stagehand"
- ]
+ ]
- },
+ },
- "steps": {
+ "steps": {
- "type": "array",
+ "type": "array",
- "items": {
+ "items": {
- "type": "object",
+ "type": "object",
- "properties": {
+ "properties": {
- "index": {
+ "index": {
- "type": "integer",
+ "type": "integer",
- "minimum": 0
+ "minimum": 0
- },
+ },
- "type": {
+ "type": {
- "type": "string",
+ "type": "string",
- "enum": [
+ "enum": [
- "goto",
+ "goto",
- "click",
+ "click",
- "fill",
+ "fill",
- "press",
+ "press",
- "wait",
+ "wait",
- "wait_for",
+
|
|
tests/mcp-concurrency-e2e.test.ts > Real MCP server stdio: 5 parallel list_personas calls > dispatches all 5 successfully and returns valid responses:
tests/mcp-concurrency-e2e.test.ts#L228
Error: timeout waiting for MCP responses
❯ Timeout._onTimeout tests/mcp-concurrency-e2e.test.ts:228:28
|
|
tests/logger.test.ts > logger > falls back to info when LOG_LEVEL is invalid:
tests/logger.test.ts#L132
Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-test-sBt68v'
❯ tests/logger.test.ts:132:10
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -4051, code: 'ENOTEMPTY', syscall: 'rmdir', path: 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-test-sBt68v' }
|
|
tests/logger.test.ts > logger > respects LOG_LEVEL=warn (info suppressed, warn emitted):
tests/logger.test.ts#L104
Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-test-3uC5Cd'
❯ tests/logger.test.ts:104:10
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -4051, code: 'ENOTEMPTY', syscall: 'rmdir', path: 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-test-3uC5Cd' }
|
|
Unhandled error:
tests/logger.test.ts#L169
Error: EPERM: operation not permitted, lstat 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-tLzUyL\log.ndjson'
❯ Timeout._onTimeout tests/logger.test.ts:169:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -4048, code: 'EPERM', syscall: 'lstat', path: 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-tLzUyL\log.ndjson' }
This error originated in "tests/logger.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "redacts secret embedded in the log message itself". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
Unhandled error:
tests/logger.test.ts#L169
Error: EPERM: operation not permitted, lstat 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-b5sybU\log.ndjson'
❯ Timeout._onTimeout tests/logger.test.ts:169:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -4048, code: 'EPERM', syscall: 'lstat', path: 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-b5sybU\log.ndjson' }
This error originated in "tests/logger.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "redacts secret in nested arrays / objects". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
Unhandled error:
tests/logger.test.ts#L169
Error: EPERM: operation not permitted, lstat 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-qcD2XB\log.ndjson'
❯ Timeout._onTimeout tests/logger.test.ts:169:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -4048, code: 'EPERM', syscall: 'lstat', path: 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-qcD2XB\log.ndjson' }
This error originated in "tests/logger.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "redacts a registered secret value found inside a string field". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
Unhandled error:
tests/logger.test.ts#L169
Error: EPERM: operation not permitted, lstat 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-RpFHLi\log.ndjson'
❯ Timeout._onTimeout tests/logger.test.ts:169:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -4048, code: 'EPERM', syscall: 'lstat', path: 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-RpFHLi\log.ndjson' }
This error originated in "tests/logger.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "does nothing when no secrets registered". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
Unhandled error:
tests/logger.test.ts#L169
Error: EPERM: operation not permitted, lstat 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-rQ0d82\log.ndjson'
❯ Timeout._onTimeout tests/logger.test.ts:169:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -4048, code: 'EPERM', syscall: 'lstat', path: 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-rQ0d82\log.ndjson' }
This error originated in "tests/logger.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "does not censor unrelated fields". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
Unhandled error:
tests/logger.test.ts#L169
Error: EPERM: operation not permitted, lstat 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-llYbAd\log.ndjson'
❯ Timeout._onTimeout tests/logger.test.ts:169:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -4048, code: 'EPERM', syscall: 'lstat', path: 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-llYbAd\log.ndjson' }
This error originated in "tests/logger.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "redacts one-level-nested apiKey". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
Unhandled error:
tests/logger.test.ts#L169
Error: EPERM: operation not permitted, lstat 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-NP8YTK\log.ndjson'
❯ Timeout._onTimeout tests/logger.test.ts:169:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -4048, code: 'EPERM', syscall: 'lstat', path: 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-NP8YTK\log.ndjson' }
This error originated in "tests/logger.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "redacts top-level password / token / cookie / authorization". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
Unhandled error:
tests/logger.test.ts#L169
Error: EPERM: operation not permitted, lstat 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-SXOcRm\log.ndjson'
❯ Timeout._onTimeout tests/logger.test.ts:169:16
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -4048, code: 'EPERM', syscall: 'lstat', path: 'C:\Users\RUNNER~1\AppData\Local\Temp\logger-redact-SXOcRm\log.ndjson' }
This error originated in "tests/logger.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "redacts top-level apiKey field". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
Test (ubuntu-latest · Node 18)
Process completed with exit code 1.
|
|
Test (windows-latest · Node 18)
Process completed with exit code 1.
|
|
Test (macos-13 · Node 20)
Canceling since a higher priority waiting request for ci-CI-refs/pull/7/merge exists
|
|
Test (macos-13 · Node 22)
Canceling since a higher priority waiting request for ci-CI-refs/pull/7/merge exists
|
|
CI
Canceling since a higher priority waiting request for ci-CI-refs/pull/7/merge exists
|
|
Test (macos-13 · Node 18)
Canceling since a higher priority waiting request for ci-CI-refs/pull/7/merge exists
|
|
Test (ubuntu-latest · Node 22)
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/
|
|
Test (ubuntu-latest · Node 20)
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/
|
|
Test (macos-14 · Node 22)
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/
|
|
Test (macos-14 · Node 20)
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/
|
|
Test (macos-14 · Node 18)
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/
|
|
Test (windows-latest · Node 22)
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/
|
|
Test (windows-latest · Node 20)
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/
|
|
Test (ubuntu-latest · Node 18)
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/
|
|
Test (windows-latest · Node 18)
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/
|