Skip to content

Add Spatial aggregations #12948

Add Spatial aggregations

Add Spatial aggregations #12948

Triggered via pull request April 21, 2026 14:20
Status Success
Total duration 35m 23s
Artifacts 7

ide-pull-request.yml

on: pull_request
🔍 GUI Files Changed  /  Changed Files
9s
🔍 GUI Files Changed / Changed Files
🔍 IDE Files Changed  /  Changed Files
9s
🔍 IDE Files Changed / Changed Files
🔍 Engine Files Changed  /  Changed Files
7s
🔍 Engine Files Changed / Changed Files
📦 Package  /  Build Backend (linux, amd64)
10m 35s
📦 Package / Build Backend (linux, amd64)
📦 Package  /  Build Backend (windows, amd64)
19m 12s
📦 Package / Build Backend (windows, amd64)
📦 Package  /  GUI build (linux, amd64)
1m 4s
📦 Package / GUI build (linux, amd64)
📦 Package  /  GUI build (windows, amd64)
2m 26s
📦 Package / GUI build (windows, amd64)
📦 Package  /  Package New IDE (linux, amd64)
11m 39s
📦 Package / Package New IDE (linux, amd64)
📦 Package  /  Package New IDE (windows, amd64)
15m 45s
📦 Package / Package New IDE (windows, amd64)
IDE Required Checks
3s
IDE Required Checks
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
🔍 Engine Files Changed / Changed Files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, step-security/changed-files@v45. 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/
🔍 GUI Files Changed / Changed Files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, step-security/changed-files@v45. 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/
🔍 IDE Files Changed / Changed Files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, step-security/changed-files@v45. 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/
📦 Package / GUI build (linux, amd64)
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/github-script@v7, actions/upload-artifact@v4, bazel-contrib/setup-bazel@0.15.0. 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/
📦 Package / GUI build (windows, amd64)
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/github-script@v7, bazel-contrib/setup-bazel@0.15.0. 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/
📦 Package / Build Backend (linux, amd64)
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/github-script@v7, actions/upload-artifact@v4, bazel-contrib/setup-bazel@0.15.0. 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/
📦 Package / Build Backend (windows, amd64)
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/github-script@v7, actions/upload-artifact@v4, bazel-contrib/setup-bazel@0.15.0. 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/
📦 Package / Package New IDE (linux, amd64)
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/download-artifact@v4, actions/github-script@v7, actions/upload-artifact@v4, bazel-contrib/setup-bazel@0.15.0. 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/
📦 Package / Package New IDE (windows, amd64)
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/download-artifact@v4, actions/github-script@v7, actions/upload-artifact@v4, bazel-contrib/setup-bazel@0.15.0. 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/

Artifacts

Produced during runtime
Name Size Digest
Edition File
785 Bytes
sha256:2f9e646c0c5ce08f5e41627a1d336f5928a8d52b1a633e9576d9c9cf62ff2672
backend-linux
784 MB
sha256:1479cc1a8d946010b85f7e846034b0e5dc38f25639bb55d0b44c868060154737
backend-windows
764 MB
sha256:5c7b6d3ac9278c1827f9cffa401011886b4a5491cddc636a5f845f8a39bc15d2
fbs-schema
1.74 KB
sha256:a471c987ec17ae35208f1fc7790063971d641e2a529c46223d730c02a93d6b55
gui
14.4 MB
sha256:5f9a608fd143f41e2d938809409d89de6418c4d17c8187a1a03a60104bffa855
ide-linux
888 MB
sha256:d7a9708c86dce4bd1db6c2c699e22824efc3eecf95c54299de59d9902b94aefd
ide-windows
893 MB
sha256:88634a58845bbbeee09714bf517f0f936d1d1550b8318a808fa732f6170105d5