Skip to content

feat: add new endpoints for fetching feature flags and feature subgraphs by federated graph #5579

feat: add new endpoints for fetching feature flags and feature subgraphs by federated graph

feat: add new endpoints for fetching feature flags and feature subgraphs by federated graph #5579

Triggered via pull request April 7, 2026 17:12
Status Success
Total duration 2m 28s
Artifacts 2

query-planner-ci.yaml

on: pull_request
check-labels-and-engine-changes
16s
check-labels-and-engine-changes
filter-changes
6s
filter-changes
build_test
6s
build_test
get_pr_url
0s
get_pr_url
comment-on-failure
0s
comment-on-failure
comment-on-success
0s
comment-on-success
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
filter-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@v2. 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/
check-labels-and-engine-changes
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/setup-go@v5. 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/
check-labels-and-engine-changes
Restore cache failed: Dependencies file is not found in /home/runner/work/cosmo/cosmo. Supported file pattern: go.sum
build-cli
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4.0.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/
build-router
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior: router/Dockerfile#L48
RedundantTargetPlatform: Setting platform to predefined ${TARGETPLATFORM} in FROM is redundant as this is the default behavior More info: https://docs.docker.com/go/dockerfile/rule/redundant-target-platform/
Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior: router/Dockerfile#L34
RedundantTargetPlatform: Setting platform to predefined ${TARGETPLATFORM} in FROM is redundant as this is the default behavior More info: https://docs.docker.com/go/dockerfile/rule/redundant-target-platform/

Artifacts

Produced during runtime
Name Size Digest
wgc-experimental-5f4720f835eb466b83f7d4953c39e03b7bfaa449-bun-linux-x64
41.9 MB
sha256:2cbf38d2359cd686fee9f3ae97214045372d4ffb640ad22fe341dab4ac9a2e4c
wundergraph~cosmo~CLVM3U.dockerbuild
73.9 KB
sha256:15b9c4971e579e06f97c807d3635bf1d5ac4a4fd7f9b9dfe2e8421d72fdc3887