Skip to content

chore: update package versions to include post-release tags#8955

Merged
ogabrielluiz merged 1 commit into
mainfrom
bump-post1
Jul 9, 2025
Merged

chore: update package versions to include post-release tags#8955
ogabrielluiz merged 1 commit into
mainfrom
bump-post1

Conversation

@ogabrielluiz
Copy link
Copy Markdown
Contributor

@ogabrielluiz ogabrielluiz commented Jul 9, 2025

  • 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

  • Chores
    • Updated project version to 1.5.0.post1 to reflect a post-release iteration.
    • Adjusted dependency specification for "langflow-base" to allow patch-level updates within the 0.5.x series.

* 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.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 9, 2025

Walkthrough

The 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

File(s) Change Summary
pyproject.toml Updated version to "1.5.0.post1"; changed "langflow-base" dependency from "==0.5.0" to "~=0.5.0"
src/backend/base/pyproject.toml Updated version to "0.5.0.post1"

Suggested labels

size:S, lgtm, ignore-for-release

Suggested reviewers

  • edwinjosechittilappilly
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch bump-post1

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
🪧 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.
    • Explain this complex logic.
    • 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. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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.

Documentation and Community

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

@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Jul 9, 2025
@ogabrielluiz ogabrielluiz requested a review from Cristhianzl July 9, 2025 17:26
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
pyproject.toml (1)

20-20: ~=0.5.0 widens the constraint – verify lock-file regeneration
Switching from ==0.5.0 to the compatible release operator allows any 0.5.x (including future minor bug-fixes). That’s usually desirable, but remember to:

  1. Regenerate uv.lock so CI/CD and local dev environments resolve to the same new version.
  2. Re-run the test-suite against the resolved 0.5.0.post1 to 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

📥 Commits

Reviewing files that changed from the base of the PR and between 73c1f20 and 34be8e0.

⛔ Files ignored due to path filters (1)
  • uv.lock is 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 calls get_version_info()["version"] (e.g. in main.py and api/utils.py), so there’s no hard-coded __version__ constant to update. Bumping version = "0.5.0.post1" in pyproject.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
Ensure src/backend/langflow/__init__.py (or equivalent) exports __version__ = "1.5.0.post1" so that the package metadata and runtime agree.

Copy link
Copy Markdown
Member

@Cristhianzl Cristhianzl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@dosubot dosubot Bot added the lgtm This PR has been approved by a maintainer label Jul 9, 2025
@ogabrielluiz ogabrielluiz added the fast-track Skip tests and sends PR into the merge queue label Jul 9, 2025
@ogabrielluiz ogabrielluiz enabled auto-merge July 9, 2025 17:55
@ogabrielluiz ogabrielluiz added this pull request to the merge queue Jul 9, 2025
Cristhianzl

This comment was marked as duplicate.

Merged via the queue into main with commit be25e88 Jul 9, 2025
46 of 47 checks passed
@ogabrielluiz ogabrielluiz deleted the bump-post1 branch July 9, 2025 18:07
smatiolids pushed a commit to smatiolids/langflow-dev that referenced this pull request Jul 10, 2025
…-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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fast-track Skip tests and sends PR into the merge queue ignore-for-release lgtm This PR has been approved by a maintainer size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants