Skip to content

ci: upgrade vercel cli version to newer (#7267) #1896

ci: upgrade vercel cli version to newer (#7267)

ci: upgrade vercel cli version to newer (#7267) #1896

Triggered via push April 16, 2026 16:44
Status Success
Total duration 8m 15s
Artifacts 6
Build Frontend Image  /  Build and verify flagsmith-frontend image
2m 19s
Build Frontend Image / Build and verify flagsmith-frontend image
Build API Image  /  Build and verify flagsmith-api image
2m 56s
Build API Image / Build and verify flagsmith-api image
Build Private Cloud API Image  /  Build and verify flagsmith-private-cloud-api image
3m 0s
Build Private Cloud API Image / Build and verify flagsmith-private-cloud-api image
Build Private Cloud Image  /  Build and verify flagsmith-private-cloud image
3m 4s
Build Private Cloud Image / Build and verify flagsmith-private-cloud image
Build Unified Image  /  Build and verify flagsmith image
3m 1s
Build Unified Image / Build and verify flagsmith image
Build E2E Image  /  Build flagsmith-e2e image
1m 20s
Build E2E Image / Build flagsmith-e2e image
Build API Test Image  /  Build flagsmith-api-test image
2m 7s
Build API Test Image / Build flagsmith-api-test image
Build API Enterprise Test Image  /  Build flagsmith-api-private-test image
1m 59s
Build API Enterprise Test Image / Build flagsmith-api-private-test image
Matrix: run-e2e-tests
docker-publish-api  /  publish
docker-publish-api / publish
docker-publish-frontend  /  publish
docker-publish-frontend / publish
docker-publish-unified  /  publish
docker-publish-unified / publish
docker-publish-quay-frontend  /  publish
docker-publish-quay-frontend / publish
docker-publish-private-cloud-api  /  publish
docker-publish-private-cloud-api / publish
docker-publish-quay-enterprise-api  /  publish
docker-publish-quay-enterprise-api / publish
docker-publish-private-cloud  /  publish
docker-publish-private-cloud / publish
docker-publish-quay-enterprise  /  publish
docker-publish-quay-enterprise / publish
update-charts
update-charts
Fit to window
Zoom out
Zoom in

Annotations

21 warnings
Build API Enterprise Test Image / Build flagsmith-api-private-test image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@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/
Build API Enterprise Test Image / Build flagsmith-api-private-test image
Back off 16.582 seconds before retry.
Build API Enterprise Test Image / Build flagsmith-api-private-test image
Failed to download action 'https://api.github.com/repos/docker/login-action/tarball/c94ce9fb468520275223c153574b00df6fe4bcc9'. Error: The request was canceled due to the configured HttpClient.Timeout of 15 seconds elapsing.
Build E2E Image / Build flagsmith-e2e image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@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/
Build API Test Image / Build flagsmith-api-test image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@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/
Build Frontend Image / Build and verify flagsmith-frontend image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4, actions/upload-artifact@v4, docker/login-action@v3, docker/metadata-action@v5, github/codeql-action/upload-sarif@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/
Build Frontend Image / Build and verify flagsmith-frontend image
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
Build API Image / Build and verify flagsmith-api image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4, actions/upload-artifact@v4, docker/login-action@v3, docker/metadata-action@v5, github/codeql-action/upload-sarif@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/
Build API Image / Build and verify flagsmith-api image
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
Build Private Cloud API Image / Build and verify flagsmith-private-cloud-api image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4, actions/upload-artifact@v4, docker/login-action@v3, docker/metadata-action@v5, github/codeql-action/upload-sarif@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/
Build Private Cloud API Image / Build and verify flagsmith-private-cloud-api image
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
Build Unified Image / Build and verify flagsmith image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4, actions/upload-artifact@v4, docker/login-action@v3, docker/metadata-action@v5, github/codeql-action/upload-sarif@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/
Build Unified Image / Build and verify flagsmith image
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
Build Private Cloud Image / Build and verify flagsmith-private-cloud image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4, actions/upload-artifact@v4, docker/login-action@v3, docker/metadata-action@v5, github/codeql-action/upload-sarif@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/
Build Private Cloud Image / Build and verify flagsmith-private-cloud image
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
run-e2e-tests (depot-ubuntu-latest-16, ghcr.io/flagsmith/flagsmith-api:main, --grep @oss) / E2E
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-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/
run-e2e-tests (depot-ubuntu-latest-arm-16, ghcr.io/flagsmith/flagsmith-api:main, --grep @oss) / E2E
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-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/
run-e2e-tests (depot-ubuntu-latest-arm-16, ghcr.io/flagsmith/flagsmith-private-cloud-api:main, --... / E2E
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-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/
run-e2e-tests (depot-ubuntu-latest-16, ghcr.io/flagsmith/flagsmith-private-cloud-api:main, --grep... / E2E
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dawidd6/action-download-artifact@v6, docker/login-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/
run-e2e-tests (depot-ubuntu-latest-16, ghcr.io/flagsmith/flagsmith-private-cloud-api:main, --grep... / E2E
Failed to download action 'https://api.github.com/repos/marocchino/sticky-pull-request-comment/tarball/773744901bac0e8cbb5a0dc842800d45e9b2b405'. Error: The request was canceled due to the configured HttpClient.Timeout of 15 seconds elapsing.

Artifacts

Produced during runtime
Name Size Digest
flagsmith-api-trivy-results
639 Bytes
sha256:a24f197e69aee9af76902119252e07b0b838f5bc1982de6589db1f98fcf71746
flagsmith-frontend-trivy-results
646 Bytes
sha256:aecb59b427f1224bdc448e6ee861f2e2181d70f3978768909e32d85448c0ead7
flagsmith-private-cloud-api-trivy-results
651 Bytes
sha256:563eda2a28a8995a2ef2588e6a2aed11122f625cf2e7fcc316937136e1b937a7
flagsmith-private-cloud-trivy-results
649 Bytes
sha256:ac712bc8773e78f09f9aac68790849a90ee8af6454bfb264024b6d1dc628a85b
flagsmith-trivy-results
637 Bytes
sha256:9c0534f2fa281bc212730ea031bc54888824fea956714ab0a600eee3917c5d7d
visual-regression-baselines
1.8 MB
sha256:284ab091a780fc0721eb2607289dd9340292d27c01aef0f477fc91f526d73897