Skip to content

ci: update nightly script to support other version operators#8980

Merged
ogabrielluiz merged 1 commit into
mainfrom
fix-nightly-pep440
Jul 10, 2025
Merged

ci: update nightly script to support other version operators#8980
ogabrielluiz merged 1 commit into
mainfrom
fix-nightly-pep440

Conversation

@ogabrielluiz
Copy link
Copy Markdown
Contributor

@ogabrielluiz ogabrielluiz commented Jul 10, 2025

Updated the regex pattern in update_uv_dependency.py to accommodate both ~= and == version specifiers alongside PEP 440 version suffixes. This change improves the flexibility and accuracy of dependency updates for the langflow-base package.

Summary by CodeRabbit

  • Chores
    • Improved detection of "langflow-base" dependency versions in configuration files to support both exact and compatible release specifiers.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 10, 2025

Caution

Review failed

The pull request is closed.

"""

Walkthrough

The regular expression in the update_uv_dependency.py script was updated to match both exact (==) and compatible (~=) version specifiers for the "langflow-base" dependency in pyproject.toml, while maintaining support for PEP 440 version suffixes. No changes were made to function signatures.

Changes

File(s) Change Summary
scripts/ci/update_uv_dependency.py Updated regex to match both == and ~= for "langflow-base" dependency version specifiers.

Possibly related PRs

Suggested labels

lgtm, fast-track
"""

Suggested reviewers

  • jordanrfrazier

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c5083a5 and 49c319b.

📒 Files selected for processing (1)
  • scripts/ci/update_uv_dependency.py (1 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix-nightly-pep440

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 10, 2025
…rt both ~= and == version specifiers

Updated the regex pattern in update_uv_dependency.py to accommodate both ~= and == version specifiers alongside PEP 440 version suffixes. This change improves the flexibility and accuracy of dependency updates for the langflow-base package.
@ogabrielluiz ogabrielluiz merged commit 75e930d into main Jul 10, 2025
12 of 13 checks passed
@ogabrielluiz ogabrielluiz deleted the fix-nightly-pep440 branch July 10, 2025 13:02
smatiolids pushed a commit to smatiolids/langflow-dev that referenced this pull request Jul 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant