Skip to content

Conversation

@jan-janssen
Copy link
Member

@jan-janssen jan-janssen commented Jan 25, 2026

Summary by CodeRabbit

  • Chores
    • Updated runtime dependencies to newer, compatible versions: numpy (2.3.3 → 2.4.1 overall; some files 2.3.5→2.4.1), matplotlib (3.10.6 → 3.10.8), and pysqa (0.3.3 → 0.3.4).
    • Updated project metadata to reflect the new dependency versions used in CI and packaging.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 25, 2026

📝 Walkthrough

Walkthrough

Updated dependency versions in CI environment and packaging files: numpy bumped (mostly to 2.4.1, one file to 2.3.5), matplotlib bumped in integration, and pysqa bumped to 0.3.4. No changes to control flow, logic, or exported/public APIs.

Changes

Cohort / File(s) Summary
CI/CD Environment: integration
./.ci_support/environment-integration.yml
Bumped numpy 2.3.3 → 2.3.5, matplotlib 3.10.6 → 3.10.8, and pysqa 0.3.3 → 0.3.4.
CI/CD Environment: mini / windows
./.ci_support/environment-mini.yml, ./.ci_support/environment-win.yml
Bumped numpy 2.3.3 → 2.4.1.
CI/CD Environment: MPI variants
./.ci_support/environment-mpich.yml, ./.ci_support/environment-openmpi.yml
Bumped numpy 2.3.3 → 2.4.1 and pysqa 0.3.3 → 0.3.4.
Packaging / project metadata
pyproject.toml
Updated pysqa in optional dependency lists from 0.3.3 → 0.3.4.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

🐰 I nibble lines and tweak the feed,
NumPy hops forward with speedy speed,
Matplotlib sparkles in the night,
Pysqa tiptoes, version light.
Hooray — upgrades make my codegarden bright! 🥕

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main changes: updating numpy, matplotlib, and pysqa dependencies across multiple environment configuration files and pyproject.toml.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks 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

Comment @coderabbitai help to get the list of available commands and usage tips.

@jan-janssen jan-janssen marked this pull request as draft January 25, 2026 12:25
@codecov
Copy link

codecov bot commented Jan 25, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.42%. Comparing base (575a482) to head (4e03f2a).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #891   +/-   ##
=======================================
  Coverage   93.42%   93.42%           
=======================================
  Files          38       38           
  Lines        1840     1840           
=======================================
  Hits         1719     1719           
  Misses        121      121           

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

@jan-janssen jan-janssen marked this pull request as ready for review January 25, 2026 13:22
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: 1

🤖 Fix all issues with AI agents
In `@pyproject.toml`:
- Around line 54-61: The pyproject extras list references a non-existent package
version "pysqa==0.3.4" in the cluster and all extras; update those entries (the
strings "pysqa==0.3.4" inside the cluster and all arrays) to the available
version "pysqa==0.3.3" or remove the pysqa entries if you intend to wait for a
future release, ensuring both the cluster and all extras are kept consistent.

Comment on lines 54 to 61
cluster = [
"pysqa==0.3.3",
"pysqa==0.3.4",
"h5py==3.15.1",
]
all = [
"mpi4py==4.1.1",
"pysqa==0.3.3",
"pysqa==0.3.4",
"h5py==3.15.1",
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

pysqa 0.3.4 pypi python version requirements

💡 Result:

pysqa==0.3.4 is not available on PyPI (the latest PyPI release is 0.3.3, released Oct 20, 2025). For pysqa on PyPI, the declared Python requirement is:

  • Python >= 3.9, < 3.15. [1]

Replace pysqa 0.3.4 with the available version 0.3.3 (or remove if 0.3.4 is planned for future release).
pysqa 0.3.4 does not exist on PyPI; the latest release is 0.3.3 (Oct 20, 2025). The specification at lines 55 and 60 will fail installation. Update to pysqa==0.3.3 or document if this change is contingent on an upcoming release.

🤖 Prompt for AI Agents
In `@pyproject.toml` around lines 54 - 61, The pyproject extras list references a
non-existent package version "pysqa==0.3.4" in the cluster and all extras;
update those entries (the strings "pysqa==0.3.4" inside the cluster and all
arrays) to the available version "pysqa==0.3.3" or remove the pysqa entries if
you intend to wait for a future release, ensuring both the cluster and all
extras are kept consistent.

@jan-janssen jan-janssen merged commit 41d76ff into main Jan 25, 2026
61 of 63 checks passed
@jan-janssen jan-janssen deleted the numpy branch January 25, 2026 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants