[Maintenance] Update pyzmq to 27.0.0

[jan-janssen]

Summary by CodeRabbit

• Chores
  • Updated the version of the pyzmq package to 27.0.0 across all environment and configuration files.

[coderabbitai]

Walkthrough

This update raises the pyzmq package version from various 26.x.x releases to 27.0.0 across all environment configuration files and the pyproject.toml. No other dependencies or configuration settings were changed, aside from a newline at the end of pyproject.toml.

Changes

Files	Summary
.ci_support/environment-docs.yml .ci_support/environment-integration.yml .ci_support/environment-mini.yml .ci_support/environment-mpich.yml .ci_support/environment-openmpi.yml .ci_support/environment-win.yml binder/environment.yml	Updated pyzmq version to 27.0.0
pyproject.toml	Updated pyzmq version to 27.0.0 and added a newline at EOF

Possibly related PRs

• Bump pyzmq from 26.0.3 to 26.1.0 #386: Updates pyzmq version across environment files and pyproject.toml from 26.0.3 to 26.1.0.
• Bump pyzmq from 26.1.0 to 26.1.1 #392: Bumps pyzmq version in multiple configuration files and pyproject.toml from 26.1.0 to 26.1.1.
• Bump pyzmq from 26.1.1 to 26.2.0 #394: Advances pyzmq version in the same set of files from 26.2.0 to 27.0.0.

Suggested labels

dependencies

Poem

🐇
A hop and a skip, a version anew,
pyzmq’s number just grew!
From twenty-six to twenty-seven—
Dependency gardens freshly leaven.
With every bump, our code will run
Smoother, brighter—oh what fun!
🌱✨

---

📜 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 c81d7a2 and 2cbdea7.

📒 Files selected for processing (8)

• .ci_support/environment-docs.yml (1 hunks)
• .ci_support/environment-integration.yml (1 hunks)
• .ci_support/environment-mini.yml (1 hunks)
• .ci_support/environment-mpich.yml (1 hunks)
• .ci_support/environment-openmpi.yml (1 hunks)
• .ci_support/environment-win.yml (1 hunks)
• binder/environment.yml (1 hunks)
• pyproject.toml (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (14)

• GitHub Check: unittest_openmpi (ubuntu-latest, 3.11)
• GitHub Check: unittest_openmpi (ubuntu-latest, 3.12)
• GitHub Check: unittest_mpich (macos-latest, 3.13)
• GitHub Check: unittest_openmpi (ubuntu-latest, 3.13)
• GitHub Check: unittest_openmpi (macos-latest, 3.13)
• GitHub Check: notebooks_integration
• GitHub Check: unittest_win
• GitHub Check: unittest_flux_openmpi
• GitHub Check: unittest_mpich (ubuntu-latest, 3.11)
• GitHub Check: unittest_mpich (ubuntu-latest, 3.12)
• GitHub Check: unittest_flux_mpich
• GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-mpich.yml)
• GitHub Check: unittest_old
• GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-openmpi.yml)

🔇 Additional comments (10)

.ci_support/environment-win.yml (2)

9-9: Validate pyzmq version bump
The version was updated to 27.0.0. Please confirm that conda-forge provides pyzmq 27.0.0 for all targeted platforms to prevent CI failures.

---

1-17:

✅ Verification successful

Ensure complete sync of all env specs
The PR summary mentions updates in other CI YAMLs plus environment-mini.yml and binder/environment.yml. Run a grep to catch any missing pyzmq references and verify those files are included in this PR:

---

🏁 Script executed:

#!/bin/bash
rg -l "pyzmq\s*="

Length of output: 57

---

🏁 Script executed:

#!/bin/bash
echo "binder/environment.yml pyzmq entries:"
rg -n "pyzmq" binder/environment.yml || echo "No matches in binder/environment.yml"

echo
echo "pyproject.toml pyzmq entries:"
rg -n "pyzmq" pyproject.toml || echo "No matches in pyproject.toml"

Length of output: 292

---

🏁 Script executed:

#!/bin/bash
# Locate environment-mini.yml and check for pyzmq entries
file=$(find . -type f -name "environment-mini.yml")
if [[ -z "$file" ]]; then
  echo "environment-mini.yml not found in repository"
else
  echo "Found environment-mini.yml at $file"
  echo
  echo "pyzmq entries in $file:"
  rg -n "pyzmq" "$file" || echo "No pyzmq entries in $file"
fi

Length of output: 461

---

All pyzmq references are in sync at version 27.0.0
Verified that every environment spec and manifest includes the same pyzmq =27.0.0 entry:

• .ci_support/environment-win.yml: - pyzmq =27.0.0
• .ci_support/environment-mini.yml: - pyzmq =27.0.0
• binder/environment.yml: - pyzmq =27.0.0
• pyproject.toml: "pyzmq==27.0.0" (lines 6 & 34)

No missing or mismatched entries detected.

.ci_support/environment-integration.yml (1)

10-10: Confirm bump consistency
The pyzmq version now matches other CI environments. No conflicts spotted here.

.ci_support/environment-docs.yml (1)

14-14: Confirm bump consistency
This update is in line with the other CI YAML files.

.ci_support/environment-mpich.yml (1)

9-9: Confirm bump consistency
The pyzmq version aligns with the other environment configs.

.ci_support/environment-openmpi.yml (1)

9-9: Confirm bump consistency
Matches the version bump applied across CI configurations.

pyproject.toml (2)

6-6: Bump pyzmq in build-system requirements
Updated pyzmq to 27.0.0 as part of the version upgrade.

---

34-34: Bump pyzmq in project dependencies
Updated pyzmq to 27.0.0 to align with the build system configuration.

.ci_support/environment-mini.yml (1)

7-7: Update pyzmq version for mini CI environment
Pinning pyzmq to 27.0.0 is consistent with other CI environment configurations.

binder/environment.yml (1)

9-9: Align pyzmq version in Binder environment
Upgraded pyzmq to 27.0.0 to match the version bump across all environment files.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.78%. Comparing base (c81d7a2) to head (2cbdea7).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #679   +/-   ##
=======================================
  Coverage   96.78%   96.78%           
=======================================
  Files          29       29           
  Lines        1307     1307           
=======================================
  Hits         1265     1265           
  Misses         42       42           

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