Skip to content

fix(eql): return the node itself from every json_tree subtree read #1571

fix(eql): return the node itself from every json_tree subtree read

fix(eql): return the node itself from every json_tree subtree read #1571

Triggered via pull request October 24, 2026 08:25
Status Success
Total duration 15m 4s
Artifacts –

test-eql.yml

on: pull_request
Detect relevant changes
7s
Detect relevant changes
Compute matrix
4s
Compute matrix
SQL doc validation
38s
SQL doc validation
known-failure markers
10s
known-failure markers
doc anchor links
9s
doc anchor links
Build test archive
7m 28s
Build test archive
JSON Schema validation
46s
JSON Schema validation
Rust workspace crates
2m 22s
Rust workspace crates
Encrypted-domain codegen
31s
Encrypted-domain codegen
eql_v3 self-containment
40s
eql_v3 self-containment
Matrix coverage inventory
4m 10s
Matrix coverage inventory
Supabase splinter
39s
Supabase splinter
Matrix: rust-encryption-postgres
Matrix: validate
e2e property suite (fresh encryption)
7m 38s
e2e property suite (fresh encryption)
Matrix: test
ci-required
4s
ci-required
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Detect relevant changes
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: dorny/paths-filter@0e4a8c6effa4802afeda77dc8d303f8176d7dfad. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
eql-bindings not verified against the registry
The stack-encrypt version eql-bindings names is not on crates.io yet, so the packaged crate could not be built against the registry here. release-plz builds it at publish time (publish_all_features in packages/eql/release-plz.toml) and refuses to publish eql-bindings until that stack-encrypt has shipped.
Build test archive
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Shard PG17 3/4
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Shard PG17 4/4
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Shard PG17 2/4
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Shard PG17 1/4
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/