chore: support Python 3.14 by ogabrielluiz · Pull Request #13085 · langflow-ai/langflow

ogabrielluiz · 2026-05-12T18:00:41Z

Summary

Adds Python 3.14 support to langflow's supported version range and gates PR merges on 3.14 CI passing.

Changes

requires-python bumped to <3.15 in all 4 workspace packages: langflow, langflow-base, lfx, langflow-sdk.

Conditional pins for the two deps without 3.14 wheels at their existing caps:

onnxruntime: >=1.26 on 3.14 (existing <1.24 cap retained for 3.10 compat)
faiss-cpu: >=1.13.2 on 3.14 (existing ==1.9.0.post1 retained for older Pythons)

CI matrices updated to include 3.14:

ci.yml PR default: ['3.10', '3.14'] (gates every PR on 3.14)
python_test.yml, nightly_build.yml, release.yml, release-lfx.yml, integration_tests.yml, lint-py.yml: full sweep now 3.10–3.14

Known upstream gaps

A handful of optional-extra packages still pin their own python_version<'3.14' and will be skipped or warn on 3.14 installs until upstreams catch up: IBM watsonx ecosystem (langchain-ibm, ibm-watsonx-ai, ibm-watsonx-orchestrate-*, cuga), langwatch, langchain-pinecone, gepa, ragstack-ai-knowledge-store. langchain-core also emits a runtime warning on 3.14 because pydantic.v1 is not 3.14-compatible.

Core langflow + lfx install and import cleanly on 3.14.2 locally.

CI cost note

Adding 3.14 to the PR default roughly doubles backend test cost per PR. We can offset later by dropping 3.10 once 3.14 is stable.

## Changes - Update pyproject.toml: requires-python from <3.14 to <3.15 - Update all 5 Dockerfiles to use Python 3.14: - Builder stage: python3.12-trixie-slim → python3.14-trixie-slim - Runtime stage: python:3.12-slim-trixie → python:3.14-slim-trixie ## Files Updated - src/backend/base/pyproject.toml - docker/build_and_push_base.Dockerfile - docker/build_and_push.Dockerfile - docker/build_and_push_backend.Dockerfile - docker/build_and_push_with_extras.Dockerfile - docker/build_and_push_ep.Dockerfile ## Rationale Python 3.14.5 was released on May 10, 2026. Upgrading to the latest Python version should help reduce CVE vulnerabilities in Docker images. ## Testing Strategy This is an experimental change to test Python 3.14 compatibility: - Docker images will use Python 3.14 - CI/CD workflows still test on Python 3.10-3.13 - Nightly build will validate if dependencies work with 3.14 - Can be reverted quickly if issues are found ## Next Steps - Monitor nightly build for failures - If successful, update CI/CD workflows to add Python 3.14 to test matrix - If failures occur, revert and investigate compatibility issues

Bump requires-python upper bound to <3.15 across langflow, langflow-base, lfx, and langflow-sdk, and add 3.14 to CI test matrices so PRs are gated on 3.14 compatibility. Conditional pins for transitive deps without 3.14 wheels at the existing caps: - onnxruntime: >=1.26 on 3.14 (existing <1.24 cap retained for 3.10) - faiss-cpu: >=1.13.2 on 3.14 (existing ==1.9.0.post1 retained for <3.14)

coderabbitai · 2026-05-12T18:00:52Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9a25758e-5622-4b1d-b5b1-4c287eebddf8

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

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch chore/python-3.14

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.}

jordanrfrazier

lgtm - we can add in docker updates or merge them separately - https://github.com/langflow-ai/langflow/pull/13083/changes

codecov · 2026-05-12T18:10:03Z

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 54.46%. Comparing base (ea29bcc) to head (6e54e98).

Files with missing lines	Patch %	Lines
src/lfx/src/lfx/services/settings/base.py	0.00%	1 Missing and 1 partial ⚠️
src/lfx/src/lfx/utils/concurrency.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@                Coverage Diff                 @@
##           release-1.10.0   #13085      +/-   ##
==================================================
- Coverage           54.59%   54.46%   -0.13%     
==================================================
  Files                2140     2140              
  Lines              199789   199732      -57     
  Branches            30123    28420    -1703     
==================================================
- Hits               109084   108794     -290     
- Misses              89523    89756     +233     
  Partials             1182     1182

Flag	Coverage Δ
backend	`59.86% <ø> (-0.07%)`	⬇️
frontend	`54.38% <ø> (-0.18%)`	⬇️
lfx	`49.30% <0.00%> (+<0.01%)`	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/lfx/src/lfx/utils/concurrency.py	`75.67% <0.00%> (ø)`
src/lfx/src/lfx/services/settings/base.py	`72.56% <0.00%> (-0.29%)`	⬇️

... and 53 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.

…thon-3.14

github-actions · 2026-05-12T18:22:23Z

Frontend Unit Test Coverage Report

Coverage Summary

Lines	Statements	Branches	Functions
	38.21% (47496/124282)	67.7% (6480/9571)	38.02% (1088/2861)

Unit Test Results

Tests	Skipped	Failures	Errors	Time
4278	0 💤	0 ❌	0 🔥	9m 56s ⏱️

ibm-watsonx-ai 1.3.x cannot import on Python 3.14: its StrEnum subclasses override __init__ in a way that conflicts with 3.14's reworked enum __set_name__ path (TypeError on KnowledgeBaseFieldRole class creation). Cap ibm-watsonx-ai, langchain-ibm, and the ibm-watsonx-orchestrate-* extras at python_version<'3.14' until upstream adapts. Watsonx component imports are already lazy, so this surfaces only at component-access time on 3.14, where the existing ImportError handler in lfx.components.ibm.__init__ degrades it gracefully. test_model_utils.py imports ChatWatsonx at module top to verify get_model_name resolves model_id; guard that import so the test module skips on 3.14 instead of breaking collection.

build_and_push*.Dockerfile already moved to 3.14 in the merge from feat/upgrade-python-3.14-docker-images. Apply the same bump to the dev, devcontainer, and lfx Docker images so all in-repo Dockerfiles share one Python version.

cuga (and its transitive fastembed -> py-rust-stemmers source build), altk/agent-lifecycle-toolkit (re-pulls ibm-watsonx-ai which was already gated), langchain-pinecone, langwatch, ragstack-ai-knowledge-store, and OpenDsStar all pin themselves below 3.14 upstream. Without a marker guard, the workspace lock still tries to install them and a Docker `uv sync` then attempts source builds that require Rust (CI Docker test failure with py-rust-stemmers 0.1.5). Add python_version<'3.14' (or <'3.13' for ragstack) to each pin so those packages are simply omitted from the 3.14 install set until upstream catches up. uv pip check is now clean on 3.14.2.

Python 3.14 tightened PurePath.__init__ to reject unknown keyword arguments. The KeyedWorkerLockManager constructor was passing ensure_exists=True to Path() instead of user_cache_dir(), which silently worked on 3.10-3.13 but raises TypeError on 3.14 and also meant the cache directory was never actually being created. Move the kwarg to user_cache_dir() where it belongs and update the two unit tests that asserted the buggy call shape.

Resolve auto-generated artifact conflicts (.secrets.baseline timestamp and component_index.json's toolguard pin) by keeping PR-side values; both reflect the PR's already-rebuilt state and match its uv.lock.

Python 3.14's zipfile.is_zipfile() now validates the central-directory signature in addition to EOCD, so the garbage+EOCD payload no longer passes the is_zipfile() dispatch in the /flows/upload/ route. The endpoint still returns 400 with a descriptive detail (now from the JSON branch); only the message wording differs, which the test was asserting verbatim.

Pydantic-settings on Python 3.14 parses the env var '*' into ['*'] before the cors_origins field validator runs (the list[str] | str union resolves differently than on 3.10-3.13). Collapse that back to the bare-string wildcard so downstream consumers — including warn_about_future_cors_changes and the test suite — see the same shape on every supported Python version.

…n-3.14 # Conflicts: # pyproject.toml

* feat: upgrade Docker images to Python 3.14 (experimental) - Update pyproject.toml: requires-python from <3.14 to <3.15 - Update all 5 Dockerfiles to use Python 3.14: - Builder stage: python3.12-trixie-slim → python3.14-trixie-slim - Runtime stage: python:3.12-slim-trixie → python:3.14-slim-trixie - src/backend/base/pyproject.toml - docker/build_and_push_base.Dockerfile - docker/build_and_push.Dockerfile - docker/build_and_push_backend.Dockerfile - docker/build_and_push_with_extras.Dockerfile - docker/build_and_push_ep.Dockerfile Python 3.14.5 was released on May 10, 2026. Upgrading to the latest Python version should help reduce CVE vulnerabilities in Docker images. This is an experimental change to test Python 3.14 compatibility: - Docker images will use Python 3.14 - CI/CD workflows still test on Python 3.10-3.13 - Nightly build will validate if dependencies work with 3.14 - Can be reverted quickly if issues are found - Monitor nightly build for failures - If successful, update CI/CD workflows to add Python 3.14 to test matrix - If failures occur, revert and investigate compatibility issues * chore: support Python 3.14 Bump requires-python upper bound to <3.15 across langflow, langflow-base, lfx, and langflow-sdk, and add 3.14 to CI test matrices so PRs are gated on 3.14 compatibility. Conditional pins for transitive deps without 3.14 wheels at the existing caps: - onnxruntime: >=1.26 on 3.14 (existing <1.24 cap retained for 3.10) - faiss-cpu: >=1.13.2 on 3.14 (existing ==1.9.0.post1 retained for <3.14) * chore: marker-gate IBM watsonx packages for Python 3.14 ibm-watsonx-ai 1.3.x cannot import on Python 3.14: its StrEnum subclasses override __init__ in a way that conflicts with 3.14's reworked enum __set_name__ path (TypeError on KnowledgeBaseFieldRole class creation). Cap ibm-watsonx-ai, langchain-ibm, and the ibm-watsonx-orchestrate-* extras at python_version<'3.14' until upstream adapts. Watsonx component imports are already lazy, so this surfaces only at component-access time on 3.14, where the existing ImportError handler in lfx.components.ibm.__init__ degrades it gracefully. test_model_utils.py imports ChatWatsonx at module top to verify get_model_name resolves model_id; guard that import so the test module skips on 3.14 instead of breaking collection. * [autofix.ci] apply automated fixes * chore: upgrade remaining Docker images to Python 3.14 build_and_push*.Dockerfile already moved to 3.14 in the merge from feat/upgrade-python-3.14-docker-images. Apply the same bump to the dev, devcontainer, and lfx Docker images so all in-repo Dockerfiles share one Python version. * [autofix.ci] apply automated fixes * chore: gate 3.14-broken extras to python_version<'3.14' cuga (and its transitive fastembed -> py-rust-stemmers source build), altk/agent-lifecycle-toolkit (re-pulls ibm-watsonx-ai which was already gated), langchain-pinecone, langwatch, ragstack-ai-knowledge-store, and OpenDsStar all pin themselves below 3.14 upstream. Without a marker guard, the workspace lock still tries to install them and a Docker `uv sync` then attempts source builds that require Rust (CI Docker test failure with py-rust-stemmers 0.1.5). Add python_version<'3.14' (or <'3.13' for ragstack) to each pin so those packages are simply omitted from the 3.14 install set until upstream catches up. uv pip check is now clean on 3.14.2. * test: skip test_altk_agent on Python 3.14 altk (agent-lifecycle-toolkit) is gated to python_version<'3.14' upstream and now via the langflow-base [altk] extra marker. The test imports altk at module top to exercise ALTKAgentComponent; guard the import so collection skips on 3.14 instead of failing. * test: skip remaining altk tests on Python 3.14 Three more test modules import lfx.base.agents.altk_* at module top, which transitively imports altk. Add the same module-level skip guard as test_altk_agent.py: - test_altk_agent_logic.py - test_altk_agent_tool_conversion.py - test_conversation_context_ordering.py * fix(calculator): replace removed ast.Num with ast.Constant for Python 3.14 ast.Num was deprecated in Python 3.8 in favor of ast.Constant and removed entirely in 3.14. The calculator tool and its core walker crashed on 3.14 with 'module ast has no attribute Num'. Switch the isinstance checks to ast.Constant + isinstance(node.value, (int, float)), and drop the now-dead ast.Num backwards-compat branch in calculator_core.py (the ast.Constant branch already handles every input it would have matched). Update the parser unit-test fixtures to construct ast.Constant nodes. * [autofix.ci] apply automated fixes * [autofix.ci] apply automated fixes (attempt 2/3) * test: skip LangWatch HTTP instrumentation tests on Python 3.14 langwatch is gated to python_version<'3.14' upstream. The TestLangWatchHttpInstrumentation class patches langwatch.setup and langwatch.trace inside a fixture, which requires langwatch to be importable; on 3.14 the test errors with ModuleNotFoundError. Guard the class with a skipif on langwatch availability. * test: allow IBM and altk components to be missing on Python 3.14 test_all_modules_importable enforces that every component in __all__ imports cleanly. On 3.14 the ibm-watsonx-ai, langchain-ibm, and altk packages are gated upstream and intentionally not installed, so the WatsonxAI, WatsonxEmbeddings, and ALTKAgent components fail to import as designed. - test_all_components_in_categories_importable: accept a known-gated deny-list on 3.14 instead of failing. - test_all_lfx_component_modules_directly_importable: extend the existing 'missing optional dependency' allowlist with altk, langchain_ibm, and ibm_watsonx_ai. * fix(lfx): pass ensure_exists to user_cache_dir for Python 3.14 Python 3.14 tightened PurePath.__init__ to reject unknown keyword arguments. The KeyedWorkerLockManager constructor was passing ensure_exists=True to Path() instead of user_cache_dir(), which silently worked on 3.10-3.13 but raises TypeError on 3.14 and also meant the cache directory was never actually being created. Move the kwarg to user_cache_dir() where it belongs and update the two unit tests that asserted the buggy call shape. * [autofix.ci] apply automated fixes * test: accept either ZIP or JSON error path on Python 3.14 Python 3.14's zipfile.is_zipfile() now validates the central-directory signature in addition to EOCD, so the garbage+EOCD payload no longer passes the is_zipfile() dispatch in the /flows/upload/ route. The endpoint still returns 400 with a descriptive detail (now from the JSON branch); only the message wording differs, which the test was asserting verbatim. * fix(lfx): normalize cors_origins ['*'] back to '*' on Python 3.14 Pydantic-settings on Python 3.14 parses the env var '*' into ['*'] before the cors_origins field validator runs (the list[str] | str union resolves differently than on 3.10-3.13). Collapse that back to the bare-string wildcard so downstream consumers — including warn_about_future_cors_changes and the test suite — see the same shape on every supported Python version. --------- Co-authored-by: vijay kumar katuri <vijay.katuri@ibm.com> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com> (cherry picked from commit 1955f8f)

vjgit96 and others added 2 commits May 12, 2026 13:55

ogabrielluiz marked this pull request as ready for review May 12, 2026 18:01

ogabrielluiz requested a review from jordanrfrazier May 12, 2026 18:01

github-actions Bot added the ignore-for-release label May 12, 2026

Jkavia approved these changes May 12, 2026

View reviewed changes

github-actions Bot added the lgtm This PR has been approved by a maintainer label May 12, 2026

jordanrfrazier approved these changes May 12, 2026

View reviewed changes

ogabrielluiz added lgtm This PR has been approved by a maintainer and removed lgtm This PR has been approved by a maintainer labels May 12, 2026

Merge branch 'feat/upgrade-python-3.14-docker-images' into gabriel-py…

c457ad3

…thon-3.14

github-actions Bot added ignore-for-release and removed ignore-for-release labels May 12, 2026

[autofix.ci] apply automated fixes

394ab03

github-actions Bot added ignore-for-release and removed ignore-for-release labels May 12, 2026

chore: upgrade remaining Docker images to Python 3.14

0a1834f

build_and_push*.Dockerfile already moved to 3.14 in the merge from feat/upgrade-python-3.14-docker-images. Apply the same bump to the dev, devcontainer, and lfx Docker images so all in-repo Dockerfiles share one Python version.

github-actions Bot added ignore-for-release and removed ignore-for-release labels May 12, 2026

[autofix.ci] apply automated fixes

2f10286

github-actions Bot added ignore-for-release and removed ignore-for-release labels May 12, 2026

github-actions Bot removed the ignore-for-release label May 12, 2026

github-actions Bot added the ignore-for-release label May 12, 2026

github-actions Bot added ignore-for-release and removed ignore-for-release labels May 13, 2026

Merge branch 'release-1.10.0' into chore/python-3.14

5f6b452

Resolve auto-generated artifact conflicts (.secrets.baseline timestamp and component_index.json's toolguard pin) by keeping PR-side values; both reflect the PR's already-rebuilt state and match its uv.lock.

ogabrielluiz force-pushed the chore/python-3.14 branch from 2a91be7 to 5f6b452 Compare May 13, 2026 17:26

github-actions Bot added ignore-for-release and removed ignore-for-release labels May 13, 2026

[autofix.ci] apply automated fixes

b2b38e0

ogabrielluiz enabled auto-merge May 13, 2026 17:30

github-actions Bot added ignore-for-release and removed ignore-for-release labels May 13, 2026

ogabrielluiz added this pull request to the merge queue May 13, 2026

github-merge-queue Bot removed this pull request from the merge queue due to failed status checks May 13, 2026

Merge remote-tracking branch 'origin/release-1.10.0' into chore/pytho…

6e54e98

…n-3.14 # Conflicts: # pyproject.toml

github-actions Bot added ignore-for-release and removed ignore-for-release labels May 13, 2026

ogabrielluiz added this pull request to the merge queue May 13, 2026

Merged via the queue into release-1.10.0 with commit 1955f8f May 13, 2026
116 of 118 checks passed

ogabrielluiz deleted the chore/python-3.14 branch May 13, 2026 22:57

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore: support Python 3.14#13085

chore: support Python 3.14#13085
ogabrielluiz merged 21 commits into
release-1.10.0from
chore/python-3.14

ogabrielluiz commented May 12, 2026

Uh oh!

coderabbitai Bot commented May 12, 2026 •

edited

Loading

Review skipped

Uh oh!

jordanrfrazier left a comment

Uh oh!

codecov Bot commented May 12, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented May 12, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

ogabrielluiz commented May 12, 2026

Summary

Changes

Known upstream gaps

CI cost note

Uh oh!

coderabbitai Bot commented May 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

jordanrfrazier left a comment

Choose a reason for hiding this comment

Uh oh!

codecov Bot commented May 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

github-actions Bot commented May 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Frontend Unit Test Coverage Report

Coverage Summary

Unit Test Results

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

coderabbitai Bot commented May 12, 2026 •

edited

Loading

codecov Bot commented May 12, 2026 •

edited

Loading

github-actions Bot commented May 12, 2026 •

edited

Loading