Skip to content

ci: Add npm publish step to gnd binary build workflow #11465

ci: Add npm publish step to gnd binary build workflow

ci: Add npm publish step to gnd binary build workflow #11465

Triggered via pull request March 30, 2026 19:54
Status Cancelled
Total duration 4m 10s
Artifacts

ci.yml

on: pull_request
Run unit tests
3m 33s
Run unit tests
Subgraph Runner integration tests
3m 18s
Subgraph Runner integration tests
Run integration tests
4m 1s
Run integration tests
Check rustfmt style
18s
Check rustfmt style
Clippy linting
1m 35s
Clippy linting
Build in release mode
1m 30s
Build in release mode
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 6 warnings
Run integration tests
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6460/merge exists
Run integration tests
The operation was canceled.
Continuous Integration
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6460/merge exists
Check rustfmt style
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@v1. 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/
Build in release mode
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@v1. 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/
Clippy linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@v1. 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/
Subgraph Runner integration tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, extractions/setup-crate@v1, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
Run unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, extractions/setup-crate@v1, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
Run integration tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, extractions/setup-crate@v1, foundry-rs/foundry-toolchain@82dee4ba654bd2146511f85f0d013af94670c4de, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/