build(deps): bump num-bigint from 0.2.6 to 0.3.3 #11547
ci.yml
on: pull_request
Run unit tests
2m 24s
Subgraph Runner integration tests
1m 45s
Run integration tests
1m 42s
Check rustfmt style
19s
Clippy linting
53s
Build in release mode
56s
Annotations
50 errors and 6 warnings
|
Clippy linting:
graph/src/data/store/scalar/bigdecimal.rs#L382
mismatched types
|
|
Clippy linting:
graph/src/data/store/scalar/bigdecimal.rs#L377
mismatched types
|
|
Clippy linting:
graph/src/data/store/scalar/bigdecimal.rs#L372
mismatched types
|
|
Clippy linting:
graph/src/data/store/scalar/bigdecimal.rs#L319
mismatched types
|
|
Clippy linting:
graph/src/data/store/scalar/bigdecimal.rs#L143
mismatched types
|
|
Clippy linting:
graph/src/data/store/scalar/bigdecimal.rs#L105
mismatched types
|
|
Clippy linting:
graph/src/data/store/scalar/bigdecimal.rs#L102
mismatched types
|
|
Clippy linting:
graph/src/data/store/scalar/bigdecimal.rs#L77
no method named `to_bigint` found for struct `bigdecimal::BigDecimal` in the current scope
|
|
Clippy linting:
graph/src/data/store/scalar/bigdecimal.rs#L60
mismatched types
|
|
Clippy linting:
graph/src/data/store/scalar/bigdecimal.rs#L46
mismatched types
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Build in release mode:
graph/src/data/store/scalar/bigdecimal.rs#L77
no method named `to_bigint` found for struct `bigdecimal::BigDecimal` in the current scope
|
|
Build in release mode:
graph/src/data/store/scalar/bigdecimal.rs#L60
mismatched types
|
|
Build in release mode:
graph/src/data/store/scalar/bigdecimal.rs#L46
mismatched types
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Run integration tests:
graph/src/data/store/scalar/bigdecimal.rs#L77
no method named `to_bigint` found for struct `bigdecimal::BigDecimal` in the current scope
|
|
Run integration tests:
graph/src/data/store/scalar/bigdecimal.rs#L60
mismatched types
|
|
Run integration tests:
graph/src/data/store/scalar/bigdecimal.rs#L46
mismatched types
|
|
Run unit tests:
graph/src/data/store/scalar/bigdecimal.rs#L382
mismatched types
|
|
Run unit tests:
graph/src/data/store/scalar/bigdecimal.rs#L377
mismatched types
|
|
Run unit tests:
graph/src/data/store/scalar/bigdecimal.rs#L372
mismatched types
|
|
Run unit tests:
graph/src/data/store/scalar/bigdecimal.rs#L319
mismatched types
|
|
Run unit tests:
graph/src/data/store/scalar/bigdecimal.rs#L143
mismatched types
|
|
Run unit tests:
graph/src/data/store/scalar/bigdecimal.rs#L105
mismatched types
|
|
Run unit tests:
graph/src/data/store/scalar/bigdecimal.rs#L102
mismatched types
|
|
Run unit tests:
graph/src/data/store/scalar/bigdecimal.rs#L77
no method named `to_bigint` found for struct `bigdecimal::BigDecimal` in the current scope
|
|
Run unit tests:
graph/src/data/store/scalar/bigdecimal.rs#L60
mismatched types
|
|
Run unit tests:
graph/src/data/store/scalar/bigdecimal.rs#L46
mismatched types
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Subgraph Runner integration tests:
graph/src/data/store/scalar/bigdecimal.rs#L77
no method named `to_bigint` found for struct `bigdecimal::BigDecimal` in the current scope
|
|
|
|
|
|
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/
|
|
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/
|
|
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/
|
|
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/
|
|
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/
|
|
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/
|