Skip to content

chore(main): release 2.241.0 #17526

chore(main): release 2.241.0

chore(main): release 2.241.0 #17526

Triggered via pull request June 16, 2026 06:43
Status Success
Total duration 6m 5s
Artifacts 3

platform-pull-request.yml

on: pull_request
Check actor permissions
27s
Check actor permissions
Prepare Docker report comment
Prepare Docker report comment
Add Conventional Commit labels
Add Conventional Commit labels
Build E2E Image  /  Build flagsmith-e2e image
1m 4s
Build E2E Image / Build flagsmith-e2e image
Build API Image  /  Build and verify flagsmith-api image
1m 29s
Build API Image / Build and verify flagsmith-api image
Build Private Cloud Image  /  build
Build Private Cloud Image / build
Build Unified Image  /  Build and verify flagsmith image
1m 31s
Build Unified Image / Build and verify flagsmith image
Build Frontend Image  /  Build and verify flagsmith-frontend image
1m 27s
Build Frontend Image / Build and verify flagsmith-frontend image
Build API Test Image  /  Build flagsmith-api-test image
1m 4s
Build API Test Image / Build flagsmith-api-test image
Build API Enterprise Test Image  /  build
Build API Enterprise Test Image / build
Matrix: run-e2e-tests
Matrix: run-e2e-tests-private-cloud
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
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/metadata-action@v5. 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 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/metadata-action@v5. 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 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/metadata-action@v5, github/codeql-action/upload-sarif@v3. 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 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/metadata-action@v5, github/codeql-action/upload-sarif@v3. 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 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 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/metadata-action@v5, github/codeql-action/upload-sarif@v3. 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 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/
run-e2e-tests (depot-ubuntu-latest-16) / E2E
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: daun/playwright-report-summary@v3, marocchino/sticky-pull-request-comment@v2. 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-e2e-tests (depot-ubuntu-latest-arm-16) / E2E
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: daun/playwright-report-summary@v3, marocchino/sticky-pull-request-comment@v2. 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/

Artifacts

Produced during runtime
Name Size Digest
flagsmith-api-trivy-results
1.52 KB
sha256:a4e14c69fe84ada748c4f055976455b5ed322def63f8a1fd6b974bf3584226ff
flagsmith-frontend-trivy-results
649 Bytes
sha256:d6245b9dc1974caff8384c219e78635fcdcb2e4626268120f0e8649bb660be49
flagsmith-trivy-results
1.52 KB
sha256:249bdbbb3f1dda76bcc54ffd13973906dff7b37ee1960b68e172c00676eac6a5