Skip to content

feat: add Content-Security-Policy header and externalize theme-init #175

feat: add Content-Security-Policy header and externalize theme-init

feat: add Content-Security-Policy header and externalize theme-init #175

Re-run triggered June 16, 2026 19:16
Status Failure
Total duration 40s
Artifacts 4

ci.yml

on: pull_request
Verify prod requirements.txt is sufficient
8s
Verify prod requirements.txt is sufficient
mypy
18s
mypy
Performance benchmarks (informational)
27s
Performance benchmarks (informational)
Matrix: integration-tests
Matrix: js-tests
Matrix: lint-and-audit
Matrix: pytest
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Frontend unit tests (vitest) (macos-latest)
Process completed with exit code 1.
Frontend unit tests (vitest) (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/