Skip to content

Remove use of implicit optionality #3336

Remove use of implicit optionality

Remove use of implicit optionality #3336

Triggered via pull request May 12, 2026 17:08
Status Failure
Total duration 27m 2s
Artifacts

ci.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

42 errors, 9 warnings, and 3 notices
Build (ubuntu-latest, Node 26.x)
Process completed with exit code 1.
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits an update schema for TrackedResource by default: packages/typespec-autorest/test/options.test.ts#L412
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:412:7
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits only schema references with 'never' setting: packages/typespec-autorest/test/options.test.ts#L399
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:399:7
Build (ubuntu-latest, Node 24.x)
Process completed with exit code 1.
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits an update schema for TrackedResource by default: packages/typespec-autorest/test/options.test.ts#L412
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:412:7
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits only schema references with 'never' setting: packages/typespec-autorest/test/options.test.ts#L399
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:399:7
Build (ubuntu-latest, Node 22.x)
Process completed with exit code 1.
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits an update schema for TrackedResource by default: packages/typespec-autorest/test/options.test.ts#L412
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:412:7
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits only schema references with 'never' setting: packages/typespec-autorest/test/options.test.ts#L399
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:399:7
Build (windows-latest, Node 26.x)
Process completed with exit code 1.
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits an update schema for TrackedResource by default: packages/typespec-autorest/test/options.test.ts#L412
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:412:7
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits only schema references with 'never' setting: packages/typespec-autorest/test/options.test.ts#L399
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:399:7
Build (windows-latest, Node 24.x)
Process completed with exit code 1.
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits an update schema for TrackedResource by default: packages/typespec-autorest/test/options.test.ts#L412
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:412:7
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits only schema references with 'never' setting: packages/typespec-autorest/test/options.test.ts#L399
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:399:7
Build (windows-latest, Node 22.x)
Process completed with exit code 1.
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits an update schema for TrackedResource by default: packages/typespec-autorest/test/options.test.ts#L412
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:412:7
[@azure-tools/typespec-autorest] test/options.test.ts > typespec-autorest: options > 'emit-common-types-schema' option > emits only schema references with 'never' setting: packages/typespec-autorest/test/options.test.ts#L399
AssertionError: The expression evaluated to a falsy value: (output.definitions["WidgetUpdate"]) simple ❯ test/options.test.ts:399:7
Website
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v2. 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/
Autorest Checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v2. 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/
Build (ubuntu-latest, Node 26.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v2. 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/
Build (ubuntu-latest, Node 24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v2. 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/
Build (ubuntu-latest, Node 22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v2. 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/
Build (windows-latest, Node 26.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v2. 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/
Build (windows-latest, Node 24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v2. 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/
Build (windows-latest, Node 22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v2. 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/
E2E Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v2. 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/
Build (windows-latest, Node 26.x)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build (windows-latest, Node 24.x)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Build (windows-latest, Node 22.x)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026