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, tifffile #1253

Merged
merged 1 commit into from
Mar 17, 2025

Conversation

Czaki
Copy link
Collaborator

@Czaki Czaki commented Mar 17, 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:

  • attrs
  • coverage
  • numpy
  • partsegcore-compiled-backend
  • pyzmq
  • tifffile

Summary by Sourcery

Chores:

  • Update constraint files for multiple Python versions.

Summary by CodeRabbit

  • Chores
    • Upgraded several key dependency libraries across all supported Python environments. These improvements bring enhanced stability, performance, and better integration of upstream bug fixes—all contributing to a smoother, more reliable user experience.

@Czaki Czaki added the skip check PR title skip spellcheking PR title label Mar 17, 2025
Copy link
Contributor

sourcery-ai bot commented Mar 17, 2025

Reviewer's Guide by Sourcery

This pull request updates the constraint files for various Python versions and configurations, upgrading packages such as numpy, partsegcore-compiled-backend, and tifffile to their latest compatible versions. The changes are implemented by modifying the corresponding constraint files to reflect the new versions.

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

File-Level Changes

Change Details Files
Updates package versions in constraint files.
  • Updates numpy version.
  • Updates partsegcore-compiled-backend version.
  • Updates tifffile version.
  • Updates attrs version.
  • Updates coverage version.
  • Updates pyzmq version.
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 Mar 17, 2025

Walkthrough

This pull request updates dependency versions across multiple requirements files for Python 3.9, 3.10, 3.11, and 3.12 environments. Each file now references newer versions for packages such as attrs, coverage, numpy, partsegcore-compiled-backend, pyzmq, and tifffile. Some variations exist in the dependency list for pydantic-specific and documentation constraints files.

Changes

File(s) Change Summary
req.../constraints_py3.10{,_pydantic_1}.txt attrs: 25.1.0 → 25.3.0
coverage: 7.6.12 → 7.7.0
numpy: 2.2.3 → 2.2.4
partsegcore-compiled-backend: 0.15.11 → 0.15.12
pyzmq: 26.2.1 → 26.3.0
tifffile: 2025.2.18 → 2025.3.13
req.../constraints_py3.11{,_pydantic_1}.txt attrs: 25.1.0 → 25.3.0
coverage: 7.6.12 → 7.7.0
numpy: 2.2.3 → 2.2.4
partsegcore-compiled-backend: 0.15.11 → 0.15.12
pyzmq: 26.2.1 → 26.3.0
tifffile: 2025.2.18 → 2025.3.13
req.../constraints_py3.12{,_pydantic_1}.txt attrs: 25.1.0 → 25.3.0
coverage: 7.6.12 → 7.7.0
numpy: 2.2.3 → 2.2.4
partsegcore-compiled-backend: 0.15.11 → 0.15.12
pyzmq: 26.2.1 → 26.3.0
tifffile: 2025.2.18 → 2025.3.13
req.../constraints_py3.12_docs.txt attrs: 25.1.0 → 25.3.0
numpy: 2.2.3 → 2.2.4
partsegcore-compiled-backend: 0.15.11 → 0.15.12
pyzmq: 26.2.1 → 26.3.0
tifffile: 2025.2.18 → 2025.3.13 (Note: No update for coverage present)
req.../constraints_py3.9{,_pydantic_1}.txt attrs: 25.1.0 → 25.3.0
coverage: 7.6.12 → 7.7.0
partsegcore-compiled-backend: 0.15.11 → 0.15.12
pyzmq: 26.2.1 → 26.3.0 (Note: numpy and tifffile are not included)

Possibly related PRs

Poem

I’m just a rabbit, hopping through the code,
Updating versions on every dusty node.
Dependencies leap from old to new,
In each file, changes ring true.
With a twitch of whiskers and a joyful bound,
I celebrate these updates all around!
🐇💻

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)
  • We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
    - To enable this feature, set early_access to true under in the settings.

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.
    • 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.
  • @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 - here's some feedback:

Overall Comments:

  • Consider grouping the constraint changes by python version to improve readability.
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.

Copy link
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)
requirements/constraints_py3.10_pydantic_1.txt (1)

182-182: Ensure numpy is updated to 2.2.4
Please double-check that the numpy version in this constraints file is indeed 2.2.4 (as stated by the PR objectives) to maintain consistency with non‑pydantic constraints.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7e0a755 and 8e57efc.

📒 Files selected for processing (9)
  • requirements/constraints_py3.10.txt (6 hunks)
  • requirements/constraints_py3.10_pydantic_1.txt (6 hunks)
  • requirements/constraints_py3.11.txt (6 hunks)
  • requirements/constraints_py3.11_pydantic_1.txt (6 hunks)
  • requirements/constraints_py3.12.txt (6 hunks)
  • requirements/constraints_py3.12_docs.txt (5 hunks)
  • requirements/constraints_py3.12_pydantic_1.txt (6 hunks)
  • requirements/constraints_py3.9.txt (4 hunks)
  • requirements/constraints_py3.9_pydantic_1.txt (4 hunks)
⏰ 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 windows)
  • GitHub Check: 4DNucleome.PartSeg (Builds pyinstaller macos_arm)
  • GitHub Check: 4DNucleome.PartSeg (Builds pyinstaller_linux)
  • GitHub Check: 4DNucleome.PartSeg (Builds pyinstaller macos)
  • GitHub Check: 4DNucleome.PartSeg (Builds sdist)
  • GitHub Check: Base py3.12 / ubuntu-22.04 py 3.12 latest PyQt6
  • GitHub Check: Base py3.10 / ubuntu-20.04 py 3.10 latest PySide2
  • GitHub Check: Base py3.12 / macos-14 py 3.12 latest PyQt6
  • GitHub Check: Base py3.10 / ubuntu-22.04 py 3.10 latest PyQt5 _pydantic_1
  • GitHub Check: Base py3.11 / macos-13 py 3.11 latest PyQt5
  • GitHub Check: Base py3.10 / ubuntu-24.04 py 3.10 latest PyQt5
  • GitHub Check: Base py3.10 / ubuntu-24.04 py 3.10 latest PySide6
  • GitHub Check: Base py3.11 / windows-latest py 3.11 latest PyQt5
  • GitHub Check: Base py3.9 / ubuntu-24.04 py 3.9 latest PyQt5
  • GitHub Check: Base py3.11 / ubuntu-24.04 py 3.11 latest PyQt5
  • GitHub Check: Base py3.12 / ubuntu-24.04 py 3.12 latest PyQt5
  • 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 (manifest_check manifest_check)
  • GitHub Check: 4DNucleome.PartSeg (GetTestData linux)
  • GitHub Check: 4DNucleome.PartSeg (Documentation_check help)
  • GitHub Check: 4DNucleome.PartSeg (Documentation_check Notebook_check)
  • GitHub Check: 4DNucleome.PartSeg (formatting_check check_formating)
  • GitHub Check: Codacy Static Code Analysis
🔇 Additional comments (41)
requirements/constraints_py3.9.txt (4)

18-18: Dependency Update: attrs version bump
The version for the attrs package has been updated to 25.3.0. This change is consistent with similar updates in other constraints files. Please verify that all dependent modules continue to function as expected.


43-43: Dependency Update: coverage version bump
The coverage package is now set to version 7.7.0. Ensure that the test suites and CI pipelines are compatible with this update.


238-238: Dependency Update: partsegcore-compiled-backend upgrade
The upgrade to version 0.15.12 should be reviewed with particular attention to any compiled module integrations. A quick regression test is recommended.


353-353: Dependency Update: pyzmq version bump
Updating pyzmq to 26.3.0 appears consistent with the overall dependency bump. Please confirm that no runtime messaging/API changes lead to issues.

requirements/constraints_py3.9_pydantic_1.txt (4)

16-16: Dependency Update: attrs version bump
The attrs version has been bumped to 25.3.0. This maintains consistency with the primary constraints file.


41-41: Dependency Update: coverage version bump
Coverage is now at 7.7.0. Please ensure that the testing infrastructure remains fully compatible with this version.


236-236: Dependency Update: partsegcore-compiled-backend upgrade
The update to 0.15.12 should be checked against features relying on compiled components. A brief smoke test is advised.


350-350: Dependency Update: pyzmq version bump
The pyzmq package is updated to 26.3.0. Verify that no breaking API changes affect its usage in the project.

requirements/constraints_py3.12_docs.txt (3)

16-16: Dependency Update: attrs version bump
The attrs package has been updated to 25.3.0, aligning this docs constraint file with others.


168-168: Dependency Update: numpy version bump
The numpy version is now 2.2.4. Although this is a minor version bump, please check that the documentation builds (and any image-related examples) are still functioning correctly.


395-395: Dependency Update: tifffile version bump
Tifffile has been upgraded to 2025.3.13. Ensure that any image processing examples in the docs are validated against this release.

requirements/constraints_py3.12.txt (6)

18-18: Dependency Update: attrs version bump
Upgrading attrs to 25.3.0 helps maintain uniformity across Python version constraints. No issues are anticipated.


43-43: Dependency Update: coverage version bump
Coverage has been updated to 7.7.0. Please run the test suites to confirm that there are no new incompatibilities.


179-179: Dependency Update: numpy version bump
The numpy package is now 2.2.4—a minor update that should be backward compatible. Still, it is worth a quick check in numerical calculations.


228-228: Dependency Update: partsegcore-compiled-backend upgrade
The upgrade to 0.15.12 should be validated especially for any functions that rely on compiled backend optimizations.


342-342: Dependency Update: pyzmq version bump
With pyzmq now at 26.3.0, please ensure that existing message passing and related functionalities remain stable.


440-440: Dependency Update: tifffile version bump
Tifffile has been updated to 2025.3.13. Confirm that image file operations and processing libraries work seamlessly with this version.

requirements/constraints_py3.12_pydantic_1.txt (5)

16-16: Dependency Update: attrs version bump
Aligning attrs to version 25.3.0 here ensures consistency with other pydantic constraints. No issues are expected.


41-41: Dependency Update: coverage version bump
Coverage is now bumped to 7.7.0. Please run a quick verification with your test configuration to ensure no regressions.


226-226: Dependency Update: partsegcore-compiled-backend upgrade
The backend compiled component has been updated to 0.15.12. Validate that this upgrade does not break any interactions with pydantic models relying on it.


339-339: Dependency Update: pyzmq version bump
The upgrade to pyzmq 26.3.0 is noticed here as well. Testing for any API changes or deprecations is suggested.


437-437: Dependency Update: tifffile version bump
Tifffile has been set to 2025.3.13 in this constraints file, aligning with other environments. Ensure that pydantic-integrated image processing remains unaffected.

requirements/constraints_py3.11_pydantic_1.txt (2)

16-16: Updated attrs to 25.3.0
The version bump from 25.1.0 to 25.3.0 is correctly applied. This change is in line with the coordinated update across environments.


41-41: Updated coverage to 7.7.0
The new version of coverage is applied consistently here.

requirements/constraints_py3.10.txt (6)

18-18: Updated attrs to 25.3.0
The new version is applied on line 18.


43-43: Updated coverage to 7.7.0
This update is present on line 43 and matches the coordinated update.


185-185: Updated numpy to 2.2.4
Ensure that the Python 3.10 environment accepts the new numpy version without incompatibilities.


232-232: Updated partsegcore-compiled-backend to 0.15.12
This update is applied correctly.


349-349: Updated pyzmq to 26.3.0
The version bump is correct.


445-445: Updated tifffile to 2025.3.13
Review the release notes to ensure no breaking changes affect image processing integrations in PartSeg.

requirements/constraints_py3.10_pydantic_1.txt (5)

16-16: Updated attrs to 25.3.0
This change aligns with the other constraints files.


41-41: Updated coverage to 7.7.0
The updated version is applied as required.


232-232: Updated partsegcore-compiled-backend to 0.15.12
The dependency update is in line with the coordinated bump.


346-346: Updated pyzmq to 26.3.0
The new version is applied correctly.


442-442: Updated tifffile to 2025.3.13
Make sure to verify that the new tifffile version is compatible with any tools that depend on it.

requirements/constraints_py3.11.txt (6)

18-18: Updated attrs to 25.3.0
This change is applied correctly and is consistent with other files.


43-43: Updated coverage to 7.7.0
The new value is in place on line 43.


181-181: Updated numpy to 2.2.4
Please verify that this version is fully compatible with the PartSeg modules under Python 3.11.


230-230: Updated partsegcore-compiled-backend to 0.15.12
The value is updated as expected.


347-347: Updated pyzmq to 26.3.0
The change is applied correctly.


443-443: Updated tifffile to 2025.3.13
Verify that any downstream image processing components are tested against this update.

Copy link

codecov bot commented Mar 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.16%. Comparing base (7e0a755) to head (8e57efc).
Report is 1 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1253      +/-   ##
===========================================
+ Coverage    93.15%   93.16%   +0.01%     
===========================================
  Files          210      210              
  Lines        33288    33288              
===========================================
+ Hits         31009    31014       +5     
+ Misses        2279     2274       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Czaki Czaki added this to the 0.16.2 milestone Mar 17, 2025
@Czaki Czaki merged commit b554104 into develop Mar 17, 2025
61 checks passed
@Czaki Czaki deleted the auto-dependency-upgrades branch March 17, 2025 09:28
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