build: update langflow base dependency

[jordanrfrazier]

Updates langflow base dep to correct version.

Summary by CodeRabbit

• Chores
  • Updated a core dependency to the latest minor version, bringing upstream fixes and performance improvements.
  • Improves compatibility with newer environments while maintaining existing behavior.
  • No changes expected to user-facing features or workflows.

[coderabbitai]

Walkthrough

Bumps the langflow-base dependency version in pyproject.toml from ~0.5.0 to ~0.6.0. No other files or configurations are modified.

Changes

Cohort / File(s)	Summary
Dependency bump pyproject.toml	Update dependency constraint: langflow-base ~0.5.0 → ~0.6.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: update package versions to include post-release tags #8955 — Also modifies langflow-base version spec (to ~=0.5.0 with post-release tags), closely related packaging change.
• fix: add langchain-chroma to langflow-base #9396 — Adjusts langflow-base packaging by adding langchain-chroma; related to dependency management around langflow-base.

Suggested labels

lgtm

Suggested reviewers

• italojohnny
• Cristhianzl

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Test File Naming And Structure	⚠️ Warning	Inspected the repository’s test layout and found multiple backend tests named with the expected test_*.py pattern and structured for pytest, while frontend files bearing the *.test.ts naming (e.g., docs/technical_reference/components/workflow/nodes/OllamaTextGen.test.ts) are clearly documentation samples rather than executable tests and lack Playwright usage, meaning the naming requirement is applied to non-test artifacts, and there is no evidence of consistently documented integration-test directories or explicit setup/teardown organization across suites. Given these inconsistencies and the absence of observable coverage for negative scenarios or edge cases in the sampled files, the custom test-structure requirements are not satisfied.	Clarify which files constitute the official frontend test suite, relocate documentation examples out of test directories or rename them to avoid *.test.ts patterns, ensure integration tests are clearly marked and housed appropriately, strengthen test setup/teardown structure, and add explicit positive and negative coverage where missing before re-running this check.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly and accurately describes the main change of updating the langflow-base dependency in the build configuration, matching the changes in pyproject.toml and the PR description. It is concise and free of unnecessary details, making it clear to readers what the update entails. The use of a conventional prefix “build:” further clarifies the nature of the change.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Test Coverage For New Implementations	✅ Passed	The diff shows only a dependency version bump in pyproject.toml with no new functionality or components introduced, so there are no corresponding test files to update. Because the change is confined to configuration and does not alter code paths, the absence of new or modified tests is appropriate and consistent with the custom check’s requirements.
Test Quality And Coverage	✅ Passed	The pull request solely bumps the langflow-base dependency version in pyproject.toml without introducing any new functionality or code paths, so there are no new behaviors requiring additional tests. Existing test coverage remains appropriate for the unchanged codebase, and no async routines, API endpoints, or other features demanding specialized testing patterns were added. Consequently, there are no gaps in test quality or coverage attributable to this change.
Excessive Mock Usage Warning	✅ Passed	The pull request only updates the langflow-base dependency in pyproject.toml and does not introduce or modify any test files, so there are no new or altered mocks to evaluate; existing tests remain unchanged, implying no additional risk of excessive mocking attributable to this PR.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-lf-base

---

📜 Recent 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 a7825e1 and 5550fd5.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• pyproject.toml (1 hunks)

⏰ 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). (11)

• GitHub Check: Lint Backend / Run Mypy (3.10)
• GitHub Check: Lint Backend / Run Mypy (3.13)
• GitHub Check: Lint Backend / Run Mypy (3.12)
• GitHub Check: Lint Backend / Run Mypy (3.11)
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 2
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 4
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 5
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 3
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 1
• GitHub Check: Run Backend Tests / Integration Tests - Python 3.10
• GitHub Check: Test Starter Templates

🔇 Additional comments (1)

pyproject.toml (1)

20-20: No action needed: workspace package version satisfies ~=0.6.0
src/backend/base/pyproject.toml already declares version = "0.6.0", which meets the ~=0.6.0 requirement.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

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

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

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9999      +/-   ##
==========================================
- Coverage   23.30%   23.25%   -0.05%     
==========================================
  Files        1090     1090              
  Lines       39855    39855              
  Branches     5531     5531              
==========================================
- Hits         9289     9270      -19     
- Misses      30395    30414      +19     
  Partials      171      171              

Flag	Coverage Δ
backend	45.56% <ø> (-0.13%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 4 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.