Skip to content

feat: StyleX + Panda support, demos, and reorganized package exports #61

feat: StyleX + Panda support, demos, and reorganized package exports

feat: StyleX + Panda support, demos, and reorganized package exports #61

Triggered via pull request May 3, 2026 20:36
Status Failure
Total duration 14s
Artifacts –

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
check
Command "vp install" (cwd: /home/runner/work/squircle/squircle) exited with code 1
vp install failed
WARN  Unsupported engine: wanted: {"node":">=24.14.1"} (current: {"node":"v22.22.2","pnpm":"10.33.0"}) Scope: all 3 workspace projects  ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with <ROOT>/package/package.json Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile" Failure reason: specifiers in the lockfile don't match specifiers in package.json: * 1 dependencies were added: @pandacss/dev@>=0.40.0
check
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/