Skip to content

build(deps): bump parquet from 58.3.0 to 59.0.0 #11834

build(deps): bump parquet from 58.3.0 to 59.0.0

build(deps): bump parquet from 58.3.0 to 59.0.0 #11834

Triggered via pull request June 15, 2026 21:57
Status Failure
Total duration 7m 19s
Artifacts

ci.yml

on: pull_request
Run unit tests
1m 44s
Run unit tests
Subgraph Runner integration tests
1m 44s
Subgraph Runner integration tests
Run integration tests
2m 20s
Run integration tests
Check rustfmt style
32s
Check rustfmt style
Clippy linting
1m 40s
Clippy linting
Build in release mode
1m 22s
Build in release mode
Fit to window
Zoom out
Zoom in

Annotations

24 errors and 6 warnings
Build in release mode
Process completed with exit code 101.
Build in release mode: store/postgres/src/parquet/reader.rs#L33
expected `{closure@reader.rs:32:31}` to return `Result<RecordBatch, StoreError>`, but it returns `Result<RecordBatch, StoreError>`
Clippy linting
Process completed with exit code 101.
Clippy linting: store/postgres/src/parquet/writer.rs#L184
a value of type `std::vec::Vec<arrow::array::RecordBatch>` cannot be built from an iterator over elements of type `arrow_array::record_batch::RecordBatch`
Clippy linting: store/postgres/src/parquet/reader.rs#L33
expected `{closure@reader.rs:32:31}` to return `Result<RecordBatch, StoreError>`, but it returns `Result<RecordBatch, StoreError>`
Clippy linting: store/postgres/src/parquet/reader.rs#L33
expected `{closure@reader.rs:32:31}` to return `Result<RecordBatch, StoreError>`, but it returns `Result<RecordBatch, StoreError>`
Subgraph Runner integration tests
Process completed with exit code 101.
Subgraph Runner integration tests: store/postgres/src/parquet/reader.rs#L33
expected `{closure@reader.rs:32:31}` to return `Result<RecordBatch, StoreError>`, but it returns `Result<RecordBatch, StoreError>`
Run integration tests
Process completed with exit code 101.
Run integration tests: store/postgres/src/parquet/reader.rs#L33
expected `{closure@reader.rs:32:31}` to return `Result<RecordBatch, StoreError>`, but it returns `Result<RecordBatch, StoreError>`
Run unit tests
Process completed with exit code 101.
Run unit tests: store/postgres/src/parquet/writer.rs#L184
a value of type `Vec<arrow::array::RecordBatch>` cannot be built from an iterator over elements of type `arrow_array::record_batch::RecordBatch`
Run unit tests: store/postgres/src/parquet/reader.rs#L33
expected `{closure@reader.rs:32:31}` to return `Result<RecordBatch, StoreError>`, but it returns `Result<RecordBatch, StoreError>`
Run unit tests: store/postgres/src/parquet/reader.rs#L33
expected `{closure@reader.rs:32:31}` to return `Result<RecordBatch, StoreError>`, but it returns `Result<RecordBatch, StoreError>`
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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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 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 16th, 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/