Skip to content

Add support for retrieving plan data via useSchematicPlan hook #462

Add support for retrieving plan data via useSchematicPlan hook

Add support for retrieving plan data via useSchematicPlan hook #462

Triggered via pull request March 12, 2026 00:07
Status Failure
Total duration 1m 3s
Artifacts

pull_request_react.yml

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

Annotations

6 errors and 4 warnings
Build
Process completed with exit code 2.
Build
'"@schematichq/schematic-js"' has no exported member named 'CheckPlanReturn'. Did you mean 'CheckFlagReturn'?
Build
Property 'getPlan' does not exist on type 'Schematic'.
Build
Property 'addPlanListener' does not exist on type 'Schematic'.
Build
'"/home/runner/_work/schematic-js/schematic-js/react/node_modules/@schematichq/schematic-js/dist/schematic"' has no exported member named 'CheckPlanReturn'. Did you mean 'CheckFlagReturn'?
Build
'"/home/runner/_work/schematic-js/schematic-js/react/node_modules/@schematichq/schematic-js/dist/schematic"' has no exported member named 'CheckPlanReturn'. Did you mean 'CheckFlagReturn'?
Test (Node 25.1.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@v2.0.3. 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/
Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@v2.0.3. 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
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@v2.0.3. 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/
Test (Node 24.11.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@v2.0.3. 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/