Skip to content

chore: migrate version management to hatch-vcs #384

chore: migrate version management to hatch-vcs

chore: migrate version management to hatch-vcs #384

Triggered via pull request March 21, 2026 15:03
Status Failure
Total duration 46s
Artifacts

check-formatting.yml

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

Annotations

3 errors and 1 warning
build (3.10)
Process completed with exit code 1.
build (3.13)
The strategy configuration was canceled because "build._3_10" failed
build (3.13)
The operation was canceled.
build (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/