chore: update package versions to include post-release tags#8955
Conversation
* Bump langflow version to 1.5.0.post1 in pyproject.toml and uv.lock. * Update langflow-base version to 0.5.0.post1 in related files for consistency.
WalkthroughThe changes update the version numbers in two pyproject.toml files to post-release versions and relax the dependency requirement for "langflow-base" to allow patch-level updates. No code or public API changes were introduced. Changes
Suggested labels
Suggested reviewers
✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
pyproject.toml (1)
20-20:~=0.5.0widens the constraint – verify lock-file regeneration
Switching from==0.5.0to the compatible release operator allows any0.5.x(including future minor bug-fixes). That’s usually desirable, but remember to:
- Regenerate
uv.lockso CI/CD and local dev environments resolve to the same new version.- Re-run the test-suite against the resolved
0.5.0.post1to catch regressions early.No code change required—just a reminder to update the lock-file and pipeline.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
uv.lockis excluded by!**/*.lock
📒 Files selected for processing (2)
pyproject.toml(2 hunks)src/backend/base/pyproject.toml(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`{uv.lock,pyproject.toml}`: Use uv (>=0.4) as the Python package manager for dependency management
{uv.lock,pyproject.toml}: Use uv (>=0.4) as the Python package manager for dependency management
📄 Source: CodeRabbit Inference Engine (.cursor/rules/backend_development.mdc)
List of files the instruction was applied to:
pyproject.toml
🧠 Learnings (3)
📓 Common learnings
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test backward compatibility across Langflow versions by mapping component files to supported versions using 'VersionComponentMapping'.
src/backend/base/pyproject.toml (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test backward compatibility across Langflow versions by mapping component files to supported versions using 'VersionComponentMapping'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's REST API endpoints using the async 'client' fixture and assert correct status codes and response structure.
pyproject.toml (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test backward compatibility across Langflow versions by mapping component files to supported versions using 'VersionComponentMapping'.
🔇 Additional comments (2)
src/backend/base/pyproject.toml (1)
3-3: No manual__version__bump required – version is loaded dynamically
The code callsget_version_info()["version"](e.g. inmain.pyandapi/utils.py), so there’s no hard-coded__version__constant to update. Bumpingversion = "0.5.0.post1"inpyproject.toml(and your lockfile) ensures the runtime version reflects the new release.Likely an incorrect or invalid review comment.
pyproject.toml (1)
3-3: Same note on version constant for the top-level package
Ensuresrc/backend/langflow/__init__.py(or equivalent) exports__version__ = "1.5.0.post1"so that the package metadata and runtime agree.
…-ai#8955) * Bump langflow version to 1.5.0.post1 in pyproject.toml and uv.lock. * Update langflow-base version to 0.5.0.post1 in related files for consistency.
Summary by CodeRabbit