Skip to content

fix: use jsdelivr's content-type header to detect binary file #1531

fix: use jsdelivr's content-type header to detect binary file

fix: use jsdelivr's content-type header to detect binary file #1531

Triggered via pull request March 14, 2026 08:35
Status Success
Total duration 2m 5s
Artifacts

chromatic.yml

on: pull_request
📚 Chromatic
2m 1s
📚 Chromatic
Fit to window
Zoom out
Zoom in

Annotations

1 warning
📚 Chromatic
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: chromaui/action@5ec258af08deb3e8c36653bd618cb7fe52090031, pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/