build: upgrade to 1.7.0

[jordanrfrazier]

Upgrades all langflow packages. Ensures that nightly builds will accurately reflect that they are dev for the next released version.

e.g. the current release is 1.6.x. Nightlies should then be building as 1.7.0-devN, rather than 1.6.x-devN, since the nightly build operates off main, which contains code for the next minor version release (possibly major, but that's a larger change we'll have to manually account for).

The reason it's not updating to 1.6.x+1 is because 1) we are not "developing" on patch branches, and 2) the nightly builds run off main, so they include code for the next main release

https://peps.python.org/pep-0440/#developmental-releases

Summary by CodeRabbit

• Chores
  • Released version 1.7.0 across the main project and frontend components.
  • Updated core dependencies to latest compatible versions.
  • Backend and extension package versions updated accordingly.

[coderabbitai]

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

This PR performs a coordinated version bump across the project, updating the main project version from 1.6.4 to 1.7.0, the backend base package from 0.6.4 to 0.6.7, the lfx package from 0.1.13 to 0.2.0, and updating the langflow-base dependency constraint to ~=0.7.0.

Changes

Cohort / File(s)	Change Summary
Main project version and API spec docs/openapi/openapi.json, pyproject.toml, src/frontend/package.json	Version bumped from 1.6.4 to 1.7.0; langflow-base dependency updated from ~=0.6.4 to ~=0.7.0 in root pyproject.toml
Backend base subpackage src/backend/base/pyproject.toml	Version bumped from 0.6.4 to 0.6.7
LFX subpackage src/lfx/pyproject.toml	Version bumped from 0.1.13 to 0.2.0

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Version updates are straightforward and repetitive across multiple manifest files
• Verify that the langflow-base dependency bump to ~=0.7.0 is compatible with the codebase
• Confirm the version increments follow semver conventions (minor bumps for 1.6.4→1.7.0 and 0.1.13→0.2.0, patch bump for 0.6.4→0.6.7)

Possibly related PRs

• chore: bump versions to 1.6.4 #10129: Similar version-bump changes applied to the same manifest files in a preceding release cycle
• build: update langflow base dependency #9999: Also updates the langflow-base dependency version in pyproject.toml
• chore: Update lfx package version to 0.1.13 #10309: Previously bumped the lfx package version in src/lfx/pyproject.toml

Suggested labels

size:M, lgtm, build

Suggested reviewers

• ogabrielluiz
• deon-sanchez
• erichare

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 2 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Test Quality And Coverage	❓ Inconclusive	This PR is a version upgrade that bumps Langflow from 1.6.4 to 1.7.0 and adjusts package versions across multiple files (pyproject.toml, package.json, etc.). The changes involve only version number updates and dependency adjustments in configuration files—no new functionality or code implementations are being introduced. The custom check for "Test Quality and Coverage" is designed to evaluate tests for new implementations (async functions, API endpoints, new features), but this PR contains no new implementations to test. Instead, it references PEP 440 developmental release semantics to ensure nightly builds are properly versioned as 1.7.0-devN rather than 1.6.x-devN. Since the PR does not add new code, APIs, or functions, the test quality evaluation criteria (covering main functionality, async testing patterns, error response testing, etc.) are not applicable.	The custom check instructions are not applicable to this PR because it is a configuration/version bump PR with no new implementations. Test evaluation criteria address new features, API endpoints, and functions that require comprehensive testing, but this PR contains only version and dependency updates. To properly evaluate this PR, a different check would be needed—one focused on configuration consistency, dependency compatibility verification, and versioning correctness (as identified in the existing review comments about dependency version mismatches between pyproject.toml and src/backend/base/pyproject.toml, and the OpenAPI YAML/JSON sync issues).
Excessive Mock Usage Warning	❓ Inconclusive	The PR is a version bump PR that updates the project from version 1.6.4 to 1.7.0, touching only configuration and build files: docs/openapi/openapi.json, pyproject.toml, src/backend/base/pyproject.toml, src/frontend/package.json, and src/lfx/pyproject.toml. According to the raw summary provided, no test files have been modified in this PR, meaning there are no test implementations to review for excessive mock usage. The check for excessive mock usage in tests is not applicable to this PR since it contains only version and dependency updates without adding or modifying any test code.	The custom check "Excessive Mock Usage Warning" is designed to review test files for poor test design patterns. Since this PR contains exclusively configuration and version bump changes with no test file modifications, the check cannot be meaningfully applied. The check would be relevant for PRs that introduce or modify test code, but in this case, there are no tests to analyze. If test files are present in the repository, they should be reviewed for mock usage patterns in a separate PR analysis focused on code changes rather than version bumps.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "build: upgrade to 1.7.0" is clear, specific, and directly related to the main changes in the changeset. The title accurately reflects that the primary objective is upgrading multiple packages and components across the project to version 1.7.0, as evidenced by version bumps in the main pyproject.toml, frontend package.json, docs/openapi.json, and related backend packages. The title follows conventional commit format with the "build:" prefix, is concise without unnecessary noise, and would be immediately understood by someone reviewing the git history.
Test Coverage For New Implementations	✅ Passed	This PR is exclusively a version and dependency bump for nightly build preparation, modifying only configuration files (pyproject.toml, package.json) and the OpenAPI documentation version string. The PR introduces no functional code changes, no new components or features, and no bug fixes—it is purely a release management commit to prepare the codebase for nightly builds of version 1.7.0-devN. The custom check instructions specify that tests are required only for new functionality, components, features, or bug fixes, none of which apply to this PR. Version bump PRs following standard industry practice do not require new test files when only metadata and version numbers are updated.
Test File Naming And Structure	✅ Passed	This PR contains no test file modifications or additions as it is purely a version bump and dependency update. However, the repository already demonstrates comprehensive compliance with all test file naming and structure requirements: backend tests follow test_*.py patterns with proper pytest structure (e.g., src/backend/tests/unit/test_version.py and src/backend/tests/unit/utils/test_version.py), tests are organized into logical categories (unit, integration, backward_compatibility), test functions have descriptive names (e.g., test_compute_alpha_version, test_compute_beta_version), tests include proper setup and assertions, and existing version tests cover both positive scenarios (stable, alpha, beta, rc, post versions) and edge cases with comprehensive coverage. Frontend tests in __tests__ directories follow .test.ts/.test.tsx naming conventions as required.

---

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

[github-actions]

Frontend Unit Test Coverage Report

Coverage Summary

Lines	Statements	Branches	Functions
	14.38% (3866/26872)	7.34% (1506/20501)	8.65% (509/5881)

Unit Test Results

Tests	Skipped	Failures	Errors	Time
1549	0 💤	0 ❌	0 🔥	19.186s ⏱️

[coderabbitai]

Actionable comments posted: 3

Caution

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

⚠️ Outside diff range comments (1)

src/backend/base/pyproject.toml (1)

20-20: 🚨 CRITICAL: lfx dependency constraint incompatible with new package version.

The constraint lfx~=0.1.0 (PEP 440: >=0.1.0, ==0.1.*) will NOT accept the new lfx version 0.2.0 (bumped in src/lfx/pyproject.toml line 3). This will cause dependency resolution to fail.

Update this constraint to lfx~=0.2.0 to match the lfx package version being released.

Apply this diff to fix the dependency constraint:

 dependencies = [
-    "lfx~=0.1.0",
+    "lfx~=0.2.0",

🧹 Nitpick comments (1)

docs/openapi/openapi.json (1)

12871-12875: Optional: add leading slash to OAuth2 tokenUrl.

tokenUrl is "api/v1/login". Using "/api/v1/login" improves client generation across tools that join paths strictly.

📜 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 d707176 and 4b655fc.

⛔ Files ignored due to path filters (2)

• src/frontend/package-lock.json is excluded by !**/package-lock.json
• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (5)

• docs/openapi/openapi.json (1 hunks)
• pyproject.toml (2 hunks)
• src/backend/base/pyproject.toml (1 hunks)
• src/frontend/package.json (1 hunks)
• src/lfx/pyproject.toml (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

src/frontend/@(package*.json|tsconfig.json|tailwind.config.*|vite.config.*)

📄 CodeRabbit inference engine (.cursor/rules/frontend_development.mdc)

Frontend configuration files such as package.json, tsconfig.json, and Tailwind/Vite configs must be maintained and updated as needed.

Files:

• src/frontend/package.json

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

• GitHub Check: Lint Backend / Run Mypy (3.13)
• GitHub Check: Test Docs Build / Test Docs Build
• GitHub Check: Lint Backend / Run Mypy (3.10)
• GitHub Check: Lint Backend / Run Mypy (3.12)
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 1
• GitHub Check: Lint Backend / Run Mypy (3.11)
• GitHub Check: Run Frontend Tests / Determine Test Suites and Shard Distribution
• GitHub Check: Run Backend Tests / LFX Tests - Python 3.10
• GitHub Check: Run Frontend Unit Tests / Frontend Jest Unit Tests
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 3
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 2
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 5
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 4
• GitHub Check: Run Backend Tests / Integration Tests - Python 3.10
• GitHub Check: Test Starter Templates
• GitHub Check: build-and-deploy
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 3
• GitHub Check: Test Docker Images / Test docker images
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 5
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 4
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 1
• GitHub Check: Run Backend Tests / Unit Tests - Python 3.10 - Group 2
• GitHub Check: Run Backend Tests / Integration Tests - Python 3.10
• GitHub Check: Test Starter Templates

🔇 Additional comments (3)

src/frontend/package.json (1)

3-3: Version bump aligns with PR objectives.

The frontend package version is correctly updated to 1.7.0 alongside the coordinated project-wide version bump.

src/lfx/pyproject.toml (1)

3-3: ⚠️ Verify downstream dependency constraints before merging.

The lfx package is bumped to version 0.2.0 (minor version bump). Verify that all packages declaring lfx as a dependency have compatible version constraints. See related issues in src/backend/base/pyproject.toml.

pyproject.toml (1)

3-3: Version bump correctly increments to 1.7.0.

This aligns with the PR objective for the next development release.

[jordanrfrazier]

Might need to fix some CI. May (incorrectly) expect a released version in places that it can check out.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 31.32%. Comparing base (732ec1e) to head (9333bb6).
⚠️ Report is 1 commits behind head on main.

❌ Your project status has failed because the head coverage (39.37%) 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   #10418      +/-   ##
==========================================
- Coverage   31.33%   31.32%   -0.01%     
==========================================
  Files        1324     1324              
  Lines       59908    59908              
  Branches     8960     8960              
==========================================
- Hits        18772    18769       -3     
- Misses      40239    40242       +3     
  Partials      897      897              

Flag	Coverage Δ
backend	50.93% <ø> (-0.02%)	⬇️
frontend	13.32% <ø> (ø)
lfx	39.37% <ø> (ø)

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

[github-actions]

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft