chore: bump versions to 1.6.4

[jordanrfrazier]

Bumps versions to latest patch version 1.6.3

Summary by CodeRabbit

• Chores
  • Bumped app version to 1.6.3 across frontend and core packages.
  • Updated backend base package versioning to 0.6.3.
  • Refreshed dependency pin for langflow-base to ~=0.6.3.
  • Synchronized package metadata and versions across modules.
  • No user-facing changes or API updates.

[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

Project version metadata updated across root, backend, and frontend. Root pyproject also bumps the langflow-base dependency constraint from ~=0.6.0 to ~=0.6.3. No logic or API changes.

Changes

Cohort / File(s)	Summary of changes
Version metadata updates pyproject.toml, src/backend/base/pyproject.toml, src/frontend/package.json	Bump project versions: root 1.6.0→1.6.3, backend/base 0.6.0→0.6.3, frontend 1.6.0→1.6.3. Root also updates dependency: langflow-base =0.6.0→=0.6.3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• build: update langflow base dependency #9999 — Also updates langflow-base version in pyproject.toml (previous bump 0.5.0→0.6.0).
• chore: bump langflow version #9402 — Similar project version bumps in root and backend/base pyproject files.
• chore: update package versions to include post-release tags #8955 — Adjusts version metadata and dependency specs in pyproject/package.json files.

Suggested labels

size:XS, fast-track

Suggested reviewers

• ogabrielluiz
• italojohnny

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Test File Naming And Structure	⚠️ Warning	The repository contains numerous backend Python test files named per the test_*.py convention, but several files such as tests/integration/langchain/test_milvus.py and tests/unit/test_utils.py define multiple functions that are either skipped or cover only a single success path without corresponding failure or edge-case assertions, and a Playwright suite like src/frontend/tests/integration/app.flow.test.ts exercises solely a happy-path flow without negative coverage. These gaps indicate that tests are not comprehensively covering both positive and negative scenarios as required by the check, even though file naming and general structure appear correct. Consequently, the custom check’s criteria around coverage of edge cases and negative paths are not satisfied.	Please augment the identified backend and frontend Playwright tests with additional cases that exercise error handling, edge conditions, and failure scenarios so the suites cover both positive and negative paths, then re-run this check.
Title Check	⚠️ Warning	The pull request title indicates bumping versions to 1.6.4, but the actual changes update all version references to 1.6.3, creating a mismatch between the title and the code. This inconsistency could confuse reviewers and automated tooling that rely on the title to summarize the primary change.	Please update the pull request title to accurately reflect the version bump to 1.6.3 (or adjust the version updates in the files to 1.6.4) so that the title and changes are consistent.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Test Coverage For New Implementations	✅ Passed	I reviewed the PR and it only updates version numbers in pyproject.toml files and package.json without modifying source code or introducing new functionality, bug fixes, or components, so no corresponding tests are required. No new or updated test files are present in the diff, but given the absence of code changes there is nothing to exercise, so the custom test coverage requirements are inherently satisfied. Consequently, the PR passes the check.
Test Quality And Coverage	✅ Passed	Because the pull request only increments version numbers without introducing new functionality or API changes, there are no new behaviors that require additional automated tests, so the existing test suite remains sufficient and the check is considered satisfied.
Excessive Mock Usage Warning	✅ Passed	No test files were modified in this pull request, and the only changes are version bumps, so there is no new or altered test code that could introduce excessive mock usage; the existing tests remain unaffected, and there is no evidence of mocks obscuring test behavior in the scope of this PR.

---

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
	10.95% (2889/26373)	4.57% (926/20247)	6.51% (372/5711)

Unit Test Results

Tests	Skipped	Failures	Errors	Time
1200	0 💤	0 ❌	0 🔥	14.213s ⏱️

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 24.15%. Comparing base (4fb9ba0) to head (d724990).
⚠️ Report is 10 commits behind head on main.

❌ Your project status has failed because the head coverage (47.06%) 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   #10129      +/-   ##
==========================================
- Coverage   24.17%   24.15%   -0.02%     
==========================================
  Files        1086     1086              
  Lines       40043    40067      +24     
  Branches     5541     5546       +5     
==========================================
  Hits         9679     9679              
- Misses      30193    30217      +24     
  Partials      171      171              

Flag	Coverage Δ
backend	47.06% <ø> (-0.02%)	⬇️
frontend	10.10% <ø> (+<0.01%)	⬆️

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

[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

[github-actions]

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