Skip to content

Bump jsdom from 26.1.0 to 29.0.1 #55

Bump jsdom from 26.1.0 to 29.0.1

Bump jsdom from 26.1.0 to 29.0.1 #55

Triggered via pull request March 26, 2026 17:42
Status Failure
Total duration 46s
Artifacts

ci.yml

on: pull_request
Lint & Format
15s
Lint & Format
Python Example
7s
Python Example
Matrix: Build & Test
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 4 warnings
Lint & Format
Process completed with exit code 1.
format: packages/client/src/feedback-controller.ts#L1
File content differs from formatting output
Build & Test (22)
Process completed with exit code 1.
src/feedback.test.ts > feedback overlay > applies a custom theme from config to the overlay UI: packages/client/src/feedback.test.ts#L341
AssertionError: expected '' to be 'rgb(245, 249, 255)' // Object.is equality - Expected + Received - rgb(245, 249, 255) ❯ src/feedback.test.ts:341:38
Build & Test (20)
The strategy configuration was canceled because "build._22" failed
Build & Test (20)
Process completed with exit code 1.
src/feedback.test.ts > feedback overlay > applies a custom theme from config to the overlay UI: packages/client/src/feedback.test.ts#L341
AssertionError: expected '' to be 'rgb(245, 249, 255)' // Object.is equality - Expected + Received - rgb(245, 249, 255) ❯ src/feedback.test.ts:341:38
Python Example
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5. 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/
Lint & Format
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. 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 & Test (22)
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. 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 & Test (20)
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. 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/