Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: [Automatic] Constraints upgrades: numpy, partsegcore-compiled-backend, psygnal, qtpy, scipy, sentry-sdk #1241

Merged
merged 1 commit into from
Feb 20, 2025

Conversation

Czaki
Copy link
Collaborator

@Czaki Czaki commented Feb 10, 2025

This PR is automatically created and updated by PartSeg GitHub
action cron to keep bundle dependencies modules up to date.

The updated packages are:

  • coverage
  • dask
  • lxml
  • numpy
  • partsegcore-compiled-backend
  • psutil
  • psygnal
  • pyconify
  • pyinstaller
  • pyqt6
  • pyqt6-qt6
  • qtpy
  • scipy
  • sentry-sdk

Summary by CodeRabbit

  • Chores
    • Updated several dependency versions across our supported Python environments to the latest minor releases, delivering improved stability, enhanced performance, and bug fixes for a smoother user experience.

@Czaki Czaki added the skip check PR title skip spellcheking PR title label Feb 10, 2025
Copy link
Contributor

sourcery-ai bot commented Feb 10, 2025

Reviewer's Guide by Sourcery

This PR automatically updates the dependency constraints across multiple requirements files to ensure that the bundle dependencies are kept up-to-date. The update was triggered by a PartSeg GitHub action cron, which revises the versions of several packages.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Automated dependency updates for multiple packages
  • Updated dependency constraints for coverage, lxml, psygnal, pyconify, pyinstaller, pyqt6, and pyqt6-qt6
  • Modified constraints across various Python and Pydantic version files
  • Ensured consistency between standard and documentation requirements
requirements/constraints_py3.10.txt
requirements/constraints_py3.10_pydantic_1.txt
requirements/constraints_py3.11.txt
requirements/constraints_py3.11_pydantic_1.txt
requirements/constraints_py3.12.txt
requirements/constraints_py3.12_docs.txt
requirements/constraints_py3.12_pydantic_1.txt
requirements/constraints_py3.9.txt
requirements/constraints_py3.9_pydantic_1.txt

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Contributor

coderabbitai bot commented Feb 10, 2025

Walkthrough

This pull request updates dependency version numbers across multiple constraints files for various Python versions (3.9, 3.10, 3.11, and 3.12), including their pydantic variants and a docs-specific file. The changes adjust versions for libraries such as coverage, lxml, psygnal, pyconify, pyinstaller, pyqt6, and pyqt6-qt6. Additionally, the py3.12 files include updates for pyside6-related packages. These modifications are minor version bumps aimed at keeping the dependencies current.

Changes

Files Change Summary
requirements/constraints_py3.{9,10,11}(.txt, _pydantic_1.txt) Updated version numbers: coverage 7.6.10 → 7.6.12, dask 2025.1.0 → 2025.2.0, lxml 5.3.0 → 5.3.1, numpy 2.2.2 → 2.2.3, partsegcore-compiled-backend 0.15.9 → 0.15.11, psutil 6.1.1 → 7.0.0, psygnal 0.11.1 → 0.12.0, pyconify 0.2 → 0.2.1, pyinstaller 6.11.1 → 6.12.0, pyqt6 6.8.0 → 6.8.1, pyqt6-qt6 6.8.1 → 6.8.2, qtpy 2.4.2 → 2.4.3, scipy 1.15.1 → 1.15.2, sentry-sdk 2.20.0 → 2.21.0.
requirements/constraints_py3.12(.txt, _pydantic_1.txt) Same as above plus additional updates: pyside6, pyside6-addons, pyside6-essentials, and shiboken6 from 6.8.2 → 6.8.2.1.
requirements/constraints_py3.12_docs.txt Updated a subset of dependencies: dask 2025.1.0 → 2025.2.0, numpy 2.2.2 → 2.2.3, partsegcore-compiled-backend 0.15.9 → 0.15.11, psutil 6.1.1 → 7.0.0, psygnal 0.11.1 → 0.12.0, pyconify 0.2 → 0.2.1, pyqt6 6.8.0 → 6.8.1, pyqt6-qt6 6.8.1 → 6.8.2, qtpy 2.4.2 → 2.4.3, scipy 1.15.1 → 1.15.2, sentry-sdk 2.20.0 → 2.21.0.

Possibly related PRs

Poem

I'm a bunny with a coding beat,
Hopping through files with updates neat.
Dependencies leap from old to new,
Each version bump makes the code feel true.
With twitching whiskers and a joyful cheer,
I nibble on bugs until they're nowhere!
🐰💻 Happy coding, my dear!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f46fba8 and a66866d.

📒 Files selected for processing (9)
  • requirements/constraints_py3.10.txt (9 hunks)
  • requirements/constraints_py3.10_pydantic_1.txt (9 hunks)
  • requirements/constraints_py3.11.txt (9 hunks)
  • requirements/constraints_py3.11_pydantic_1.txt (9 hunks)
  • requirements/constraints_py3.12.txt (10 hunks)
  • requirements/constraints_py3.12_docs.txt (8 hunks)
  • requirements/constraints_py3.12_pydantic_1.txt (10 hunks)
  • requirements/constraints_py3.9.txt (8 hunks)
  • requirements/constraints_py3.9_pydantic_1.txt (8 hunks)
🚧 Files skipped from review as they are similar to previous changes (9)
  • requirements/constraints_py3.12_docs.txt
  • requirements/constraints_py3.9.txt
  • requirements/constraints_py3.10.txt
  • requirements/constraints_py3.11_pydantic_1.txt
  • requirements/constraints_py3.10_pydantic_1.txt
  • requirements/constraints_py3.12.txt
  • requirements/constraints_py3.11.txt
  • requirements/constraints_py3.9_pydantic_1.txt
  • requirements/constraints_py3.12_pydantic_1.txt
⏰ Context from checks skipped due to timeout of 300000ms (28)
  • GitHub Check: 4DNucleome.PartSeg (Tests_other test windows)
  • GitHub Check: 4DNucleome.PartSeg (Tests_other test macos)
  • GitHub Check: 4DNucleome.PartSeg (Tests_linux test_linux)
  • GitHub Check: 4DNucleome.PartSeg (Builds pyinstaller_linux)
  • GitHub Check: 4DNucleome.PartSeg (Builds pyinstaller windows)
  • GitHub Check: 4DNucleome.PartSeg (Builds pyinstaller macos_arm)
  • GitHub Check: 4DNucleome.PartSeg (Builds sdist)
  • GitHub Check: 4DNucleome.PartSeg (Builds pyinstaller macos)
  • GitHub Check: Base py3.9 / ubuntu-24.04 py 3.9 latest PyQt5
  • GitHub Check: Base py3.12 / ubuntu-24.04 py 3.12 latest PyQt5
  • GitHub Check: Base py3.12 / ubuntu-22.04 py 3.12 latest PyQt6
  • GitHub Check: Base py3.12 / macos-14 py 3.12 latest PyQt6
  • GitHub Check: Base py3.11 / windows-latest py 3.11 latest PyQt5
  • GitHub Check: Base py3.11 / ubuntu-24.04 py 3.11 latest PyQt5
  • GitHub Check: Base py3.11 / macos-13 py 3.11 latest PyQt5
  • GitHub Check: Base py3.10 / ubuntu-24.04 py 3.10 latest PySide6
  • GitHub Check: Base py3.10 / ubuntu-24.04 py 3.10 latest PyQt5
  • GitHub Check: Base py3.10 / ubuntu-20.04 py 3.10 latest PySide2
  • GitHub Check: Base py3.10 / ubuntu-22.04 py 3.10 latest PyQt5 _pydantic_1
  • GitHub Check: Test PartSeg minimal / ubuntu-24.04 py 3.9 latest PyQt5
  • GitHub Check: test_coverage / ubuntu-24.04 py 3.12 latest PyQt5
  • GitHub Check: Test PartSeg conda
  • GitHub Check: 4DNucleome.PartSeg (formatting_check check_formating)
  • GitHub Check: 4DNucleome.PartSeg (manifest_check manifest_check)
  • GitHub Check: 4DNucleome.PartSeg (Documentation_check Notebook_check)
  • GitHub Check: 4DNucleome.PartSeg (GetTestData linux)
  • GitHub Check: 4DNucleome.PartSeg (Documentation_check help)
  • GitHub Check: Codacy Static Code Analysis

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @Czaki - I've reviewed your changes and they look great!

Here's what I looked at during the review
  • 🟢 General issues: all looks good
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@Czaki Czaki force-pushed the auto-dependency-upgrades branch from f46fba8 to a66866d Compare February 17, 2025 08:18
@Czaki Czaki changed the title test: [Automatic] Constraints upgrades: psygnal test: [Automatic] Constraints upgrades: numpy, partsegcore-compiled-backend, psygnal, qtpy, scipy, sentry-sdk Feb 17, 2025
@Czaki Czaki added this to the 0.16.1 milestone Feb 17, 2025
@Czaki Czaki merged commit 0664154 into develop Feb 20, 2025
59 checks passed
@Czaki Czaki deleted the auto-dependency-upgrades branch February 20, 2025 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip check PR title skip spellcheking PR title
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant