chore: bump langflow version

[edwinjosechittilappilly]

This pull request includes minor version bumps for both the main langflow package and its langflow-base dependency. These changes update the package versions to reflect new releases.

• Version Updates:
  • Updated the langflow package version from 1.5.0.post1 to 1.5.0.post2 in pyproject.toml.
  • Updated the langflow-base package version from 0.5.0.post1 to 0.5.0.post2 in src/backend/base/pyproject.toml.

Summary by CodeRabbit

• Chores
  • Incremented application version to 1.5.0.post2.
  • Incremented backend base package version to 0.5.0.post2.
  • Patch-level maintenance update with no user-facing changes.

[coderabbitai]

Walkthrough

Bumped project version metadata in two pyproject.toml files: root project from 1.5.0.post1 to 1.5.0.post2, and src/backend/base project from 0.5.0.post1 to 0.5.0.post2. No other changes.

Changes

Cohort / File(s)	Summary of changes
Version bump: project metadata pyproject.toml, src/backend/base/pyproject.toml	Updated [project] version strings: 1.5.0.post1 → 1.5.0.post2 (root), 0.5.0.post1 → 0.5.0.post2 (backend base). No other modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: update package versions to include post-release tags #8955 — Also updates pyproject.toml version fields for a post-release bump, indicating a similar versioning change.

Suggested labels

size:XS, lgtm, fast-track

Suggested reviewers

• ogabrielluiz
• jordanrfrazier

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch patch-1.5.0.post2

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these settings in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between ede849a and 96398aa.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

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

🔇 Additional comments (1)

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

3-3: Approve: langflow-base 0.5.0.post2 bump verified — no action required

Checks performed — findings:

• src/backend/base/pyproject.toml:3 — version = "0.5.0.post2"
• pyproject.toml:3 — version = "1.5.0.post2" (root package version; separate)
• pyproject.toml:20 — dependency "langflow-base~=0.5.0" (permits post releases)
• No references to 1.5.0.post1 or 0.5.0.post1 remain

Conclusion: metadata-only bump is compatible with the root dependency pin; no changes needed.

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Root project version bumped to 1.5.0.post2 — LGTM.

Matches the base bump; dependency constraint on langflow-base "~=0.5.0" remains compatible with 0.5.0.post2.

Optionally verify consistency across the repo and absence of stale tags:

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Show updated root version:"
rg -n --glob 'pyproject.toml' $'^version\\s*=\\s*"1\\.5\\.0\\.post2"$' -n

echo
echo "Ensure no references to 1.5.0.post1 remain (expect no output):"
rg -n '1\.5\.0\.post1' || true

echo
echo "Ensure no references to 0.5.0.post1 remain (expect no output):"
rg -n '0\.5\.0\.post1' || true

Length of output: 1471

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Search for 'langflow-base' occurrences:"
rg -n "langflow-base" || true

echo
echo "Show pyproject.toml (first 240 lines):"
sed -n '1,240p' pyproject.toml || true

echo
echo "List files that still reference 1.5.0.post1:"
rg -n '1\.5\.0\.post1' || true

Length of output: 11198

---

Root version bumped to 1.5.0.post2 — stale references to 1.5.0.post1 found

pyproject.toml is updated and langflow-base ~=0.5.0 remains compatible, but the repo still contains references to 1.5.0.post1 that should be updated or confirmed intentional:

• docs/openapi.json — "version": "1.5.0.post1" (line 5)
• src/backend/base/langflow/initial_setup/starter_projects/Knowledge Retrieval.json — "lf_version" (lines 109, 226), "last_tested_version" (line 706)
• src/backend/base/langflow/initial_setup/starter_projects/Knowledge Ingestion.json — "lf_version" (lines 89, 340), "last_tested_version" (line 1049)
• src/backend/base/langflow/initial_setup/starter_projects/Instagram Copywriter.json — "last_tested_version" (line 3119)

Action: replace 1.5.0.post1 → 1.5.0.post2 in these files (or confirm they should remain), and regenerate docs/openapi.json if it’s auto-generated.