Process completed with exit code 1.

expect(received).toMatchSnapshot(hint) Snapshot name: `Components definition for table matches the snapshot: table 1` - Snapshot - 19 + Received + 4 @@ -124,46 +124,31 @@ }, { "cancelable": false, "description": "Fired when a user activates a selection controller item from the dropdown menu. The event detail contains the `id` of the activated item and, for checkbox items, - the `checked` state. + the new `checked` state. The table does not automatically modify `selectedItems`. Use this event to implement custom selection logic and update `selectedItems` accordingly.", "detailInlineType": { - "name": "ButtonDropdownProps.ItemClickDetails", + "name": "TableProps.SelectionControllerItemClickDetail", "properties": [ { "name": "checked", "optional": true, "type": "boolean", }, { - "name": "external", - "optional": true, - "type": "boolean", - }, - { - "name": "href", - "optional": true, - "type": "string", - }, - { "name": "id", "optional": false, "type": "string", }, - { - "name": "target", - "optional": true, - "type": "string", - }, ], "type": "object", }, - "detailType": "ButtonDropdownProps.ItemClickDetails", + "detailType": "TableProps.SelectionControllerItemClickDetail", "name": "onSelectionControllerItemClick", }, { "cancelable": false, "description": "Called when either the column to sort by or the direction of sorting changes upon user interaction. @@ -1002,11 +987,11 @@ The selection controller is not rendered when `selectionType` is `"single"`, when `expandableRows` with `groupSelection` is configured, or when this prop is undefined or an empty array.", "name": "selectionControllerItems", "optional": true, - "type": "ButtonDropdownProps.Items", + "type": "ReadonlyArray<TableProps.SelectionControllerItem | TableProps.SelectionControllerItemGroup>", }, { "description": "Specifies the selection type (`'single' | 'multi'`).", "inlineType": { "name": "TableProps.SelectionType", at src/__tests__/snapshot-tests/documenter.test.ts:15:24

The strategy configuration was canceled because "build._18" failed

Process completed with exit code 1.

expect(received).toMatchSnapshot(hint) Snapshot name: `Components definition for table matches the snapshot: table 1` - Snapshot - 19 + Received + 4 @@ -124,46 +124,31 @@ }, { "cancelable": false, "description": "Fired when a user activates a selection controller item from the dropdown menu. The event detail contains the `id` of the activated item and, for checkbox items, - the `checked` state. + the new `checked` state. The table does not automatically modify `selectedItems`. Use this event to implement custom selection logic and update `selectedItems` accordingly.", "detailInlineType": { - "name": "ButtonDropdownProps.ItemClickDetails", + "name": "TableProps.SelectionControllerItemClickDetail", "properties": [ { "name": "checked", "optional": true, "type": "boolean", }, { - "name": "external", - "optional": true, - "type": "boolean", - }, - { - "name": "href", - "optional": true, - "type": "string", - }, - { "name": "id", "optional": false, "type": "string", }, - { - "name": "target", - "optional": true, - "type": "string", - }, ], "type": "object", }, - "detailType": "ButtonDropdownProps.ItemClickDetails", + "detailType": "TableProps.SelectionControllerItemClickDetail", "name": "onSelectionControllerItemClick", }, { "cancelable": false, "description": "Called when either the column to sort by or the direction of sorting changes upon user interaction. @@ -1002,11 +987,11 @@ The selection controller is not rendered when `selectionType` is `"single"`, when `expandableRows` with `groupSelection` is configured, or when this prop is undefined or an empty array.", "name": "selectionControllerItems", "optional": true, - "type": "ButtonDropdownProps.Items", + "type": "ReadonlyArray<TableProps.SelectionControllerItem | TableProps.SelectionControllerItemGroup>", }, { "description": "Specifies the selection type (`'single' | 'multi'`).", "inlineType": { "name": "TableProps.SelectionType", at src/__tests__/snapshot-tests/documenter.test.ts:15:24

The strategy configuration was canceled because "build._18" failed

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 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/

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 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, github/codeql-action/analyze@v3, github/codeql-action/init@v3. 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/

Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.

CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, github/codeql-action/analyze@v3, github/codeql-action/init@v3. 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/

Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.

CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/

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/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, cloudscape-design/actions/.github/actions/patch-local-dependencies@main, cloudscape-design/actions/.github/actions/unlock-dependencies@main. 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/

Tests should not be skipped

Unexpected 'todo' comment: 'todo - investigate why resize observer...'

Unexpected 'todo' comment: 'todo: resolve split panel positioning...'

Unexpected 'todo' comment: 'TODO: Pretty-print original JSX,...'

JSX element uses aria-live property. Prefer using LiveRegion component instead

JSX element uses aria-live property. Prefer using LiveRegion component instead

JSX element uses aria-live property. Prefer using LiveRegion component instead

JSX element uses aria-live property. Prefer using LiveRegion component instead

Unexpected 'todo' comment: 'TODO: Replace this with Select'

Unexpected 'todo' comment: 'TODO: uncomment when we add...'

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/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, cloudscape-design/actions/.github/actions/patch-local-dependencies@main, cloudscape-design/actions/.github/actions/unlock-dependencies@main. 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/

Tests should not be skipped

Unexpected 'todo' comment: 'todo - investigate why resize observer...'

Unexpected 'todo' comment: 'todo: resolve split panel positioning...'

Unexpected 'todo' comment: 'TODO: Pretty-print original JSX,...'

JSX element uses aria-live property. Prefer using LiveRegion component instead

JSX element uses aria-live property. Prefer using LiveRegion component instead

JSX element uses aria-live property. Prefer using LiveRegion component instead

JSX element uses aria-live property. Prefer using LiveRegion component instead

Unexpected 'todo' comment: 'TODO: Replace this with Select'