ci: publish v2 docker images by Adam-Aghili · Pull Request #10350 · langflow-ai/langflow

Adam-Aghili · 2025-10-21T16:58:47Z

since or transition to v2 in 1.6.x we have not been publishing any of our docker images.

related: #10215

Summary by CodeRabbit

Chores
- Improved CI deployment pipeline to support per-component, multi-architecture Docker builds and registry-specific tagging across platforms.
Tests
- Updated test workflow to install the project before running tests, improving test setup and reliability.

since or transition to v2 in 1.6.x we have not been publishing any of our docker images.

coderabbitai · 2025-10-21T16:59:06Z

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Replaces the docker-build workflow matrix with per-component entries (docker-backend, docker-frontend, ghcr-backend, ghcr-frontend) including explicit dockerfile, tags, langflow_image, arch, and runner per entry; adds per-component amd64 and arm64 rows. Also adds an "Install the project" step to two Python test jobs.

Changes

Cohort / File(s)	Summary
Docker CI workflow `.github/workflows/docker-build-v2.yml`	Replaced architecture-only matrix with a per-component matrix (docker-backend, docker-frontend, ghcr-backend, ghcr-frontend). Each matrix row defines `dockerfile`, `tags`, `langflow_image`, `arch`, and `runner`. Build/push steps now use `matrix.dockerfile`, `matrix.tags`, and `matrix.langflow_image`; added amd64 and arm64 entries and corresponding runners.
Python test workflow `.github/workflows/python_test.yml`	Added an "Install the project" step (runs project install/uv sync) into the `build` and `lfx-tests` jobs after environment setup and before tests. No other logic changes.

Sequence Diagram(s)

sequenceDiagram
  participant GH as GitHub Actions
  participant Matrix as Matrix Iterator
  participant Runner as Runner (self-hosted / hosted)
  participant Docker as Docker Build
  participant Registry as Registry (Docker Hub / GHCR)

  Note over GH,Matrix: On push/PR trigger
  GH->>Matrix: expand per-component matrix rows
  Matrix->>Runner: schedule job (uses matrix.runner)
  Runner->>Docker: docker build (uses matrix.dockerfile, matrix.langflow_image)
  alt build success
    Docker->>Registry: push tags (matrix.tags) to Docker Hub / GHCR
  else build failure
    Docker->>Runner: report failure
  end

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

ci: Change docker build jobs to run on self-hosted runners #9834: Changes to GitHub Actions runner configuration for Docker build jobs (self-hosted runner adjustments).
chore: Update CI workflows to use bigger runner #9915: Modifies runner selection and ARM64/self-hosted runner handling relevant to per-architecture CI runs.
ci: allow releasing from branch #9988: Related restructuring of the .github/workflows/docker-build-v2.yml build matrix and build/push steps.

Suggested labels

enhancement, lgtm

Suggested reviewers

jordanrfrazier
ogabrielluiz

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings, 1 inconclusive)

Check name	Status	Explanation	Resolution
Test Quality And Coverage	⚠️ Warning	The pull request introduces CI workflow changes for building and publishing Docker images and tweaks the Python test setup, but it does not include any new or updated test code to verify the added build matrix or tag generation logic, nor does it update the “Run lfx tests” step to use the UV‐managed environment as recommended; as a result, there are no substantive tests covering the new functionality, no async test patterns applied, and no validations of success or error cases, indicating that test quality and coverage requirements are not met.	Add or update test suites to explicitly exercise the new Docker build and tagging logic (including both success and failure scenarios), ensure backend async functions are tested with proper pytest async patterns and run inside the UV environment, and follow existing Playwright and pytest conventions to validate behavior rather than relying on smoke‐only verifications.
Test File Naming And Structure	⚠️ Warning	The repository contains a comprehensive suite of Python backend tests following the `test_.py` naming convention with pytest imports, fixtures, and descriptive test function names, and integration tests are well organized under clearly named integration directories; however, no frontend unit tests matching `.test.ts` or `*.test.tsx` with Playwright imports were detected, indicating the absence of the required Playwright-based frontend test files and failing the specified frontend testing structure.	Add frontend unit test files named with the `.test.ts` or `.test.tsx` pattern that import from `@playwright/test` and include both positive and negative scenarios, organize them under a dedicated tests directory, and ensure each test uses descriptive names and proper setup and teardown.
Excessive Mock Usage Warning	❓ Inconclusive	I was unable to locate and analyze the project’s test files to determine the volume and context of mock usage, so I cannot assess whether mocks are being over-used in place of real objects or interactions and whether integration tests should be employed instead.	Please review the repository’s test suite to identify and quantify mock usage, ensuring that mocks are only applied to external dependencies and not core logic, and replace overly mocked unit tests with real objects or integration tests where appropriate.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly summarizes the primary update to the CI workflows by indicating that version 2 Docker images are now being published, matching the core changes in the build matrix and workflow files.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Test Coverage For New Implementations	✅ Passed	The pull request exclusively updates CI workflow definitions (.github/workflows/docker-build-v2.yml and python_test.yml) and does not introduce any new application code, bug fixes, or feature implementations that would require corresponding tests. Since there are no changes to backend or frontend code, there are no new test files expected or needed in this PR, and the existing test suite remains unaffected. Consequently, the absence of test file additions or modifications is appropriate for the scope of these CI-focused changes.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Adam-Aghili · 2025-10-21T17:00:15Z

I'll look into cleaning up repeated lines, for now I want test if the basic solution works.

coderabbitai

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cea4b42 and 31d26b3.

📒 Files selected for processing (1)

.github/workflows/docker-build-v2.yml (1 hunks)

🧰 Additional context used

🪛 actionlint (1.7.8)

.github/workflows/docker-build-v2.yml

153-153: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

167-167: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

181-181: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

195-195: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

GitHub Check: Filter Paths

🔇 Additional comments (1)

.github/workflows/docker-build-v2.yml (1)

153-153: Custom runner label requires actionlint configuration.

The custom runner label "Langflow-runner" (lines 153, 167, 181, 195) is flagged by actionlint as unknown because it's not a GitHub-provided label. If this is a self-hosted runner, configure .github/actionlint.yaml to recognize it as a custom label so the linting errors are suppressed.

Also applies to: 167-167, 181-181, 195-195

lfx cleanup error

codecov · 2025-10-21T18:11:25Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 29.59%. Comparing base (daa9565) to head (f0e40ac).
⚠️ Report is 3 commits behind head on main.

❌ Your project status has failed because the head coverage (39.36%) is below the target coverage (60.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10350      +/-   ##
==========================================
- Coverage   31.33%   29.59%   -1.75%     
==========================================
  Files        1324     1277      -47     
  Lines       59908    59462     -446     
  Branches     8960     8909      -51     
==========================================
- Hits        18771    17595    -1176     
- Misses      40239    41055     +816     
+ Partials      898      812      -86

Flag	Coverage Δ
backend	`50.95% <ø> (ø)`
lfx	`39.36% <ø> (ø)`

Flags with carried forward coverage won't be shown. Click here to find out more.
see 161 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Adam-Aghili · 2025-10-22T20:38:50Z

@coderabbitai full review

coderabbitai · 2025-10-22T20:39:27Z

✅ Actions performed

Full review triggered.

coderabbitai

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/docker-build-v2.yml (1)

227-233: Gate push steps per component + pass build-args to GHCR. Critical to avoid cross‑registry tag misuse.

Currently every matrix row runs both push steps, and both tag outputs mirror matrix.tags. This causes:

docker-* rows to also run the GHCR push with Docker Hub tags.
ghcr-* rows to run the Docker Hub push with ghcr.io/* tags.
Also, the GHCR build step misses LANGFLOW_IMAGE, diverging from Docker Hub builds.

Apply this to gate steps and align args:

@@
       - name: Login to Docker Hub
         uses: docker/login-action@v3
+        if: ${{ startsWith(matrix.component, 'docker-') }}
@@
       - name: Login to GitHub Container Registry
         uses: docker/login-action@v3
         with:
           registry: ghcr.io
           username: ${{ github.actor }}
           password: ${{ secrets.TEMP_GHCR_TOKEN}}
+        if: ${{ startsWith(matrix.component, 'ghcr-') }}
@@
-      - name: Build and push to Docker Hub
+      - name: Build and push to Docker Hub
         uses: docker/build-push-action@v6
+        if: ${{ startsWith(matrix.component, 'docker-') }}
         with:
           context: .
           push: ${{ inputs.push_to_registry }}
           file: ${{ matrix.dockerfile }}
           tags: ${{ steps.tags.outputs.docker_tags }}
           platforms: linux/${{ matrix.arch }}
           provenance: false
           cache-from: type=gha
           cache-to: type=gha,mode=max
+          build-args: |
+            LANGFLOW_IMAGE=${{ matrix.langflow_image }}
@@
-      - name: Build and push to GitHub Container Registry
+      - name: Build and push to GitHub Container Registry
         uses: docker/build-push-action@v6
+        if: ${{ startsWith(matrix.component, 'ghcr-') }}
         with:
           context: .
           push: ${{ inputs.push_to_registry }}
           file: ${{ matrix.dockerfile }}
           tags: ${{ steps.tags.outputs.ghcr_tags }}
           platforms: linux/${{ matrix.arch }}
           provenance: false
           cache-from: type=gha
           cache-to: type=gha,mode=max
+          build-args: |
+            LANGFLOW_IMAGE=${{ matrix.langflow_image }}

Also applies to: 255-279

🧹 Nitpick comments (1)

.github/workflows/docker-build-v2.yml (1)

231-232: OK switching to matrix.tags, but redundant to set both outputs.

If you gate push steps, it’s cleaner to emit only the relevant output (docker OR ghcr) to avoid confusion.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cea4b42 and 5d6a971.

📒 Files selected for processing (2)

.github/workflows/docker-build-v2.yml (4 hunks)
.github/workflows/python_test.yml (1 hunks)

🧰 Additional context used

🪛 actionlint (1.7.8)

.github/workflows/docker-build-v2.yml

153-153: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

167-167: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

181-181: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

195-195: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (644)

GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 26/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 39/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 40/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 27/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 36/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 35/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 31/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 38/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 25/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 37/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 24/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 34/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 32/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 22/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 29/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 33/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 23/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 30/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 28/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 21/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 17/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 13/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 20/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 18/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 15/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 19/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 11/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 16/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 14/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 9/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 12/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 1/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 7/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 6/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 5/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 10/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 2/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 8/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 4/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 3/40
GitHub Check: Install & Run - macos amd64 3.12
GitHub Check: Install & Run - macos amd64 3.13 (Experimental)
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 1
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.10
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.11
GitHub Check: CI / Test Starter Templates
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 26/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 39/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 40/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 27/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 36/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 35/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 31/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 38/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 25/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 37/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 24/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 34/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 32/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 22/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 29/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 33/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 23/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 30/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 28/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 21/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 17/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 13/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 20/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 18/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 15/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 19/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 11/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 16/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 14/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 9/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 12/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 1/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 7/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 6/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 5/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 10/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 2/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 8/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 4/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 3/40
GitHub Check: Install & Run - macos amd64 3.12
GitHub Check: Install & Run - macos amd64 3.13 (Experimental)
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 1
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.10
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.11
GitHub Check: CI / Test Starter Templates
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 26/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 39/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 40/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 27/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 36/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 35/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 31/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 38/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 25/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 37/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 24/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 34/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 32/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 22/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 29/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 33/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 23/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 30/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 28/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 21/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 17/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 13/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 20/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 18/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 15/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 19/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 11/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 16/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 14/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 9/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 12/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 1/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 7/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 6/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 5/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 10/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 2/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 8/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 4/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 3/40
GitHub Check: Install & Run - macos amd64 3.12
GitHub Check: Install & Run - macos amd64 3.13 (Experimental)
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 1
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.10
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.11
GitHub Check: CI / Test Starter Templates
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 26/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 39/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 40/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 27/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 36/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 35/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 31/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 38/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 25/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 37/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 24/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 34/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 32/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 22/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 29/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 33/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 23/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 30/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 28/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 21/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 17/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 13/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 20/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 18/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 15/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 19/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 11/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 16/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 14/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 9/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 12/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 1/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 7/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 6/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 5/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 10/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 2/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 8/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 4/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 3/40
GitHub Check: Install & Run - macos amd64 3.12
GitHub Check: Install & Run - macos amd64 3.13 (Experimental)
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 1
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.10
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.11
GitHub Check: CI / Test Starter Templates
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 26/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 39/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 40/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 27/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 36/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 35/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 31/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 38/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 25/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 37/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 24/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 34/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 32/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 22/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 29/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 33/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 23/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 30/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 28/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 21/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 17/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 13/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 20/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 18/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 15/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 19/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 11/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 16/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 14/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 9/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 12/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 1/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 7/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 6/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 5/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 10/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 2/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 8/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 4/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 3/40
GitHub Check: Install & Run - macos amd64 3.12
GitHub Check: Install & Run - macos amd64 3.13 (Experimental)
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 1
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.10
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.11
GitHub Check: CI / Test Starter Templates
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 26/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 39/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 40/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 27/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 36/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 35/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 31/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 38/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 25/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 37/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 24/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 34/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 32/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 22/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 29/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 33/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 23/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 30/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 28/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 21/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 17/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 13/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 20/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 18/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 15/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 19/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 11/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 16/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 14/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 9/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 12/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 1/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 7/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 6/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 5/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 10/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 2/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 8/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 4/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 3/40
GitHub Check: Install & Run - macos amd64 3.12
GitHub Check: Install & Run - macos amd64 3.13 (Experimental)
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 1
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.10
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.11
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 26/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 39/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 40/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 27/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 36/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 35/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 31/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 38/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 25/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 37/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 24/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 34/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 32/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 22/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 29/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 33/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 23/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 30/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 28/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 21/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 17/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 13/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 20/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 18/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 15/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 19/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 11/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 16/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 14/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 9/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 12/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 1/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 7/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 6/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 5/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 10/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 2/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 8/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 4/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 3/40
GitHub Check: Install & Run - macos amd64 3.12
GitHub Check: Install & Run - macos amd64 3.13 (Experimental)
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 1
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.10
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.11
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 26/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 39/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 40/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 27/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 36/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 35/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 31/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 38/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 25/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 37/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 24/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 34/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 32/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 22/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 29/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 33/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 23/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 30/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 28/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 21/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 17/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 13/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 20/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 18/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 15/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 19/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 11/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 16/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 14/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 9/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 12/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 1/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 7/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 6/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 5/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 10/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 2/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 8/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 4/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 3/40
GitHub Check: Install & Run - macos amd64 3.12
GitHub Check: Install & Run - macos amd64 3.13 (Experimental)
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 1
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.10
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.11
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 26/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 39/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 40/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 27/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 36/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 35/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 31/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 38/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 25/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 37/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 24/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 34/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 32/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 22/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 29/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 33/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 23/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 30/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 28/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 21/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 17/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 13/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 20/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 18/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 15/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 19/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 11/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 16/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 14/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 9/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 12/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 1/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 7/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 6/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 5/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 10/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 2/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 8/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 4/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 3/40
GitHub Check: Install & Run - macos amd64 3.12
GitHub Check: Install & Run - macos amd64 3.13 (Experimental)
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 1
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.10
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.11
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 26/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 39/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 40/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 27/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 36/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 35/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 31/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 38/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 25/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 37/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 24/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 34/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 32/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 22/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 29/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 23/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 30/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 28/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 21/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 17/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 13/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 20/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 18/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 15/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 19/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 11/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 16/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 14/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 9/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 12/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 1/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 7/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 6/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 5/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 10/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 2/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 8/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 4/40
GitHub Check: CI / Run Frontend Tests / Playwright Tests - Shard 3/40
GitHub Check: Install & Run - macos amd64 3.12
GitHub Check: Install & Run - macos amd64 3.13 (Experimental)
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.13 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.12 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 3
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 4
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 1
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.11 - Group 2
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 5
GitHub Check: CI / Run Backend Tests / Unit Tests - Python 3.10 - Group 1
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.10
GitHub Check: CI / Run Backend Tests / Integration Tests - Python 3.11

🔇 Additional comments (2)

.github/workflows/python_test.yml (1)

84-86: Tests already run with uv-managed venv
All test targets in the Makefile are prefixed with uv run (coverage, pytest unit and integration tests, template tests, etc.), so they already execute inside the uv virtual environment. No further changes needed.

.github/workflows/docker-build-v2.yml (1)

153-153: Verify Langflow-runner label availability

Ensure Langflow-runner is a valid runner label (self-hosted or GitHub-hosted). Without a custom actionlint config, actionlint will report it as unknown.

If it’s a self-hosted label, register it in your organization or add an actionlint.yaml listing Langflow-runner to suppress lint noise.

Also applies to lines 167, 181, and 195.

coderabbitai · 2025-10-22T20:49:21Z

+        component: [docker-backend, docker-frontend, ghcr-backend, ghcr-frontend]
        include:
-          - arch: amd64
-            runner: [Langflow-runner]
-          - arch: arm64
+          - component: docker-backend
+            dockerfile: ./docker/build_and_push_backend.Dockerfile
+            tags: langflowai/langflow-backend:${{ inputs.ref }},langflowai/langflow-backend:latest
+            langflow_image: langflowai/langflow:${{ inputs.ref }}
+            arch: amd64
+            runner: Langflow-runner
+
+          - component: docker-backend
+            dockerfile: ./docker/build_and_push_backend.Dockerfile
+            tags: langflowai/langflow-backend:${{ inputs.ref }},langflowai/langflow-backend:latest
+            langflow_image: langflowai/langflow:${{ inputs.ref }}
+            arch: arm64
+            runner: [self-hosted, linux, ARM64, langflow-ai-arm64-40gb]
+
+          - component: docker-frontend
+            dockerfile: ./docker/frontend/build_and_push_frontend.Dockerfile
+            tags: langflowai/langflow-frontend:${{ inputs.ref }},langflowai/langflow-frontend:latest
+            langflow_image: langflowai/langflow:${{ inputs.ref }}
+            arch: amd64
+            runner: Langflow-runner
+
+          - component: docker-frontend
+            dockerfile: ./docker/frontend/build_and_push_frontend.Dockerfile
+            tags: langflowai/langflow-frontend:${{ inputs.ref }},langflowai/langflow-frontend:latest
+            langflow_image: langflowai/langflow:${{ inputs.ref }}
+            arch: arm64
+            runner: [self-hosted, linux, ARM64, langflow-ai-arm64-40gb]
+
+          - component: ghcr-backend
+            dockerfile: ./docker/build_and_push_backend.Dockerfile
+            tags: ghcr.io/langflow-ai/langflow-backend:${{ inputs.ref }},ghcr.io/langflow-ai/langflow-backend:latest
+            langflow_image: ghcr.io/langflow-ai/langflow:${{ inputs.ref }}
+            arch: amd64
+            runner: Langflow-runner
+
+          - component: ghcr-backend
+            dockerfile: ./docker/build_and_push_backend.Dockerfile
+            tags: ghcr.io/langflow-ai/langflow-backend:${{ inputs.ref }},ghcr.io/langflow-ai/langflow-backend:latest
+            langflow_image: ghcr.io/langflow-ai/langflow:${{ inputs.ref }}
+            arch: arm64
+            runner: [self-hosted, linux, ARM64, langflow-ai-arm64-40gb]
+
+          - component: ghcr-frontend
+            dockerfile: ./docker/frontend/build_and_push_frontend.Dockerfile
+            tags: ghcr.io/langflow-ai/langflow-frontend:${{ inputs.ref }},ghcr.io/langflow-ai/langflow-frontend:latest
+            langflow_image: ghcr.io/langflow-ai/langflow:${{ inputs.ref }}
+            arch: amd64
+            runner: Langflow-runner
+
+          - component: ghcr-frontend
+            dockerfile: ./docker/frontend/build_and_push_frontend.Dockerfile
+            tags: ghcr.io/langflow-ai/langflow-frontend:${{ inputs.ref }},ghcr.io/langflow-ai/langflow-frontend:latest
+            langflow_image: ghcr.io/langflow-ai/langflow:${{ inputs.ref }}
+            arch: arm64
            runner: [self-hosted, linux, ARM64, langflow-ai-arm64-40gb]


⚠️ Potential issue | 🟠 Major

Avoid using raw ref in image tags; compute from version or sanitize.

Matrix tags embed ${{ inputs.ref }} which can contain invalid tag chars (e.g., slashes) and diverge from the computed version. Prefer deriving tags in a step from steps.version.outputs.version or sanitize the ref.

Option A (preferred): build tags from version in the “Set tags” step (drop per-row tags in the matrix):

- - name: Set tags - id: tags - run: | - version="${{ steps.version.outputs.version }}" - echo "docker_tags=${{ matrix.tags }}" >> $GITHUB_OUTPUT - echo "ghcr_tags=${{ matrix.tags }}" >> $GITHUB_OUTPUT + - name: Set tags + id: tags + run: | + version="${{ steps.version.outputs.version }}" + arch="${{ matrix.arch }}" + case "${{ matrix.component }}" in + docker-backend) + echo "docker_tags=langflowai/langflow-backend:${version}-${arch},langflowai/langflow-backend:latest" >> $GITHUB_OUTPUT + echo "ghcr_tags=" >> $GITHUB_OUTPUT + ;; + ghcr-backend) + echo "docker_tags=" >> $GITHUB_OUTPUT + echo "ghcr_tags=ghcr.io/langflow-ai/langflow-backend:${version}-${arch},ghcr.io/langflow-ai/langflow-backend:latest" >> $GITHUB_OUTPUT + ;; + docker-frontend) + echo "docker_tags=langflowai/langflow-frontend:${version}-${arch},langflowai/langflow-frontend:latest" >> $GITHUB_OUTPUT + echo "ghcr_tags=" >> $GITHUB_OUTPUT + ;; + ghcr-frontend) + echo "docker_tags=" >> $GITHUB_OUTPUT + echo "ghcr_tags=ghcr.io/langflow-ai/langflow-frontend:${version}-${arch},ghcr.io/langflow-ai/langflow-frontend:latest" >> $GITHUB_OUTPUT + ;; + esac

Option B: keep ref-based tags but sanitize in the step:

run: | raw="${{ inputs.ref }}" safe=$(printf '%s' "$raw" | sed 's#[^0-9A-Za-z._-]#-#g' | cut -c1-128) echo "docker_tags=${{ startsWith(matrix.component,'docker-') && format('langflowai/{0}:{1},langflowai/{0}:latest', contains(matrix.component,'frontend') && 'langflow-frontend' || 'langflow-backend', safe) || '' }}" >> $GITHUB_OUTPUT echo "ghcr_tags=${{ startsWith(matrix.component,'ghcr-') && format('ghcr.io/langflow-ai/{0}:{1},ghcr.io/langflow-ai/{0}:latest', contains(matrix.component,'frontend') && 'langflow-frontend' || 'langflow-backend', safe) || '' }}" >> $GITHUB_OUTPUT

🧰 Tools

🪛 actionlint (1.7.8)

153-153: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

167-167: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

181-181: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

195-195: label "Langflow-runner" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-11-arm", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

🤖 Prompt for AI Agents

.github/workflows/docker-build-v2.yml around lines 146-202: the matrix embeds raw `${{ inputs.ref }}` into image tags which may contain invalid characters and diverge from the computed version; remove/tag values from the per-matrix entries and instead compute sanitized tags in the "Set tags" step (preferred: use steps.version.outputs.version to construct tags and write docker_tags/ghcr_tags to $GITHUB_OUTPUT), or if you must keep ref-based tags sanitize the raw ref in that step (replace invalid chars with '-' and truncate to 128 chars) and emit the resulting tag variables for use by the build steps; update the matrix rows to no longer supply hardcoded tags and change downstream steps to read the generated docker_tags/ghcr_tags outputs.

coderabbitai · 2025-10-22T20:49:21Z

+      - name: Install the project
+        run: uv sync


🛠️ Refactor suggestion | 🟠 Major

🧩 Analysis chain

LGTM for LFX job as well; same venv caution.

Ensure lfx tests run inside the uv venv (uv run or activation) so synced deps are used.

🏁 Script executed:

#!/bin/bash # Show how lfx_tests is invoked in Makefile rg -n -C2 'lfx_tests' Makefile || true

Length of output: 793

🏁 Script executed:

#!/bin/bash # Check how lfx tests are invoked in the python_test workflow rg -n -C3 "make lfx_tests" .github/workflows/python_test.yml rg -n -C3 "uv run" .github/workflows/python_test.yml

Length of output: 211

Run LFX tests inside the UV venv
Change the “Run lfx tests” step in .github/workflows/python_test.yml (currently run: make lfx_tests) to use:

run: uv run make lfx_tests

so that the synced dependencies are loaded.

🤖 Prompt for AI Agents

.github/workflows/python_test.yml around lines 166 to 167: the "Run lfx tests" step currently executes `make lfx_tests` outside the UV virtualenv so synced dependencies aren’t loaded; update the step to run the command inside the UV venv by replacing the run value with `uv run make lfx_tests` (i.e., invoke `uv run` before the make command) so the tests execute with the synced dependencies.

add main back in update back/frontend to match orginal man logic more

* ci: publish v2 docker images since or transition to v2 in 1.6.x we have not been publishing any of our docker images. * chore: try fixing lfx cleanup error lfx cleanup error * chore: address rabbitcode comments * chore: address rabit uv comment * chore: remove build-args to see if it passes * chore: skip ci * chore: add back in LANGFLOW_IMAGE * chore: debug inputs.ref and matrix.langflow_image * chore: add {} to fix InvalidDefaultArgInForm * chore: try adding quotes * chore: try ENV LANGFLOW_IMAGE=${LANGFLOW_IMAGE} * chore: add build args to GitHub Container Registry * chore: clean up * chore: seperate out frontend and backend images * chore: update create-manifest * chore: remove ci step * chore: update release * chore: clean up * chore: clean up langflow-image * chore: revert ci removal * fix: add back in main logic update back/frontend add main back in update back/frontend to match orginal man logic more * chore: more clean up to match main * chore: remove arch from lagnflowimage for backend * chore: add misisng - for ghcr.io * chore: skip ci * chore: build_main and build_and_push_backend fixes * chore: seperate ghcr and docker publishing with if * chore: add back CI step --------- Co-authored-by: Adam Aghili <Adam.Aghili@ibm.com>

ci: publish v2 docker images

31d26b3

since or transition to v2 in 1.6.x we have not been publishing any of our docker images.

coderabbitai Bot reviewed Oct 21, 2025

View reviewed changes

ogabrielluiz requested a review from jordanrfrazier October 21, 2025 17:09

chore: try fixing lfx cleanup error

ec43e06

lfx cleanup error

chore: address rabbitcode comments

5d6a971

Merge branch 'main' into aka-missing-docker-img

a64962e

coderabbitai Bot reviewed Oct 22, 2025

View reviewed changes

Adam-Aghili added 18 commits October 22, 2025 17:03

chore: address rabit uv comment

425f29a

chore: remove build-args to see if it passes

c2298fd

chore: skip ci

830695b

chore: add back in LANGFLOW_IMAGE

d6083f5

chore: debug inputs.ref and matrix.langflow_image

7a8f001

chore: add {} to fix InvalidDefaultArgInForm

98df514

chore: try adding quotes

0c57394

chore: try ENV LANGFLOW_IMAGE=${LANGFLOW_IMAGE}

1b55f6c

chore: add build args to GitHub Container Registry

973f67b

chore: clean up

e13308e

Merge branch 'main' into aka-missing-docker-img

d76d1a6

chore: seperate out frontend and backend images

e416df7

chore: update create-manifest

5bf3429

chore: remove ci step

6178d44

chore: update release

ed5cd54

chore: clean up

5199ad0

chore: clean up langflow-image

3c36010

chore: revert ci removal

4994615

Adam-Aghili added 9 commits October 23, 2025 19:41

Merge branch 'main' into aka-missing-docker-img

bbd5f80

fix: add back in main logic update back/frontend

499158e

add main back in update back/frontend to match orginal man logic more

chore: more clean up to match main

73bd331

chore: remove arch from lagnflowimage for backend

2cc4ebc

chore: add misisng - for ghcr.io

fab2697

chore: skip ci

04b0c19

chore: build_main and build_and_push_backend fixes

9bd0e8f

Merge branch 'main' into aka-missing-docker-img

c4a9473

chore: seperate ghcr and docker publishing with if

680f63a

jordanrfrazier approved these changes Nov 3, 2025

View reviewed changes

github-actions Bot added the lgtm This PR has been approved by a maintainer label Nov 3, 2025

chore: add back CI step

f0e40ac

Adam-Aghili enabled auto-merge November 3, 2025 17:14

Adam-Aghili added this pull request to the merge queue Nov 3, 2025

github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 3, 2025

Adam-Aghili added this pull request to the merge queue Nov 3, 2025

Merged via the queue into main with commit 732ec1e Nov 3, 2025
32 of 34 checks passed

Adam-Aghili deleted the aka-missing-docker-img branch November 3, 2025 18:11

Adam-Aghili mentioned this pull request Nov 6, 2025

ci: publish v2 docker images #10521

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ci: publish v2 docker images#10350

ci: publish v2 docker images#10350
Adam-Aghili merged 32 commits into
mainfrom
aka-missing-docker-img

Adam-Aghili commented Oct 21, 2025 •

edited

Loading

Uh oh!

coderabbitai Bot commented Oct 21, 2025 •

edited

Loading

Review skipped

Uh oh!

Adam-Aghili commented Oct 21, 2025

Uh oh!

coderabbitai Bot left a comment

Uh oh!

codecov Bot commented Oct 21, 2025 •

edited

Loading

Uh oh!

Adam-Aghili commented Oct 22, 2025

Uh oh!

coderabbitai Bot commented Oct 22, 2025

Uh oh!

coderabbitai Bot left a comment

Uh oh!

coderabbitai Bot Oct 22, 2025

Uh oh!

coderabbitai Bot Oct 22, 2025

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

Adam-Aghili commented Oct 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Oct 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Walkthrough

Changes

Sequence Diagram(s)

Estimated code review effort

Possibly related PRs

Suggested labels

Suggested reviewers

Pre-merge checks and finishing touches

Uh oh!

Adam-Aghili commented Oct 21, 2025

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

codecov Bot commented Oct 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Adam-Aghili commented Oct 22, 2025

Uh oh!

coderabbitai Bot commented Oct 22, 2025

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot Oct 22, 2025

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot Oct 22, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Adam-Aghili commented Oct 21, 2025 •

edited

Loading

coderabbitai Bot commented Oct 21, 2025 •

edited

Loading

codecov Bot commented Oct 21, 2025 •

edited

Loading