Skip to content

build: replace openbabel-wheel with openbabel#974

Merged
njzjz merged 1 commit into
deepmodeling:masterfrom
njzjz-bot:openbabel-3.2
May 27, 2026
Merged

build: replace openbabel-wheel with openbabel#974
njzjz merged 1 commit into
deepmodeling:masterfrom
njzjz-bot:openbabel-3.2

Conversation

@njzjz-bot
Copy link
Copy Markdown
Contributor

@njzjz-bot njzjz-bot commented May 27, 2026

Problem

  • openbabel-wheel has been superseded by the official openbabel package.
  • Starting with Open Babel 3.2.0, users can install the Python wheels directly from openbabel on PyPI.

Change

  • Replace openbabel-wheel usage with openbabel>=3.2.0.

Notes

  • This keeps the same Python import path (openbabel) while depending on the upstream package name.

Authored by OpenClaw (model: custom-chat-jinzhezeng-group/gpt-5.5)

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions workflows to use the standard OpenBabel package specification (openbabel>=3.2.0) instead of the wheel variant across benchmark, type checking, and test pipelines.

Review Change Stack

openbabel-wheel has been superseded by the official openbabel package starting with version 3.2.0.

Authored by OpenClaw (model: custom-chat-jinzhezeng-group/gpt-5.5)
@dosubot dosubot Bot added size:XS This PR changes 0-9 lines, ignoring generated files. dependencies Pull requests that update a dependency file labels May 27, 2026
@codspeed-hq
Copy link
Copy Markdown

codspeed-hq Bot commented May 27, 2026

Merging this PR will not alter performance

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

#### 🎉 Hooray! `pytest-codspeed` just leveled up to 5.0.3!

A heads-up, this is a breaking change and it might affect your current performance baseline a bit. But here's the exciting part - it's packed with new, cool features and promises improved result stability 🥳!
Curious about what's new? Visit our releases page to delve into all the awesome details about this new version.

✅ 2 untouched benchmarks


Comparing njzjz-bot:openbabel-3.2 (e0de7b9) with master (bc617b7)

Open in CodSpeed

@codecov
Copy link
Copy Markdown

codecov Bot commented May 27, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.75%. Comparing base (bc617b7) to head (e0de7b9).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #974   +/-   ##
=======================================
  Coverage   86.75%   86.75%           
=======================================
  Files          89       89           
  Lines        8093     8093           
=======================================
  Hits         7021     7021           
  Misses       1072     1072           

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

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 27, 2026

📝 Walkthrough

Walkthrough

Three GitHub Actions workflows are updated to change how OpenBabel is installed during CI. Each workflow replaces the openbabel-wheel dependency with a version-constrained requirement openbabel>=3.2.0 in their respective uv pip install commands for benchmark, Pyright, and test jobs.

Changes

OpenBabel Dependency Updates

Layer / File(s) Summary
Replace openbabel-wheel with openbabel>=3.2.0 across workflows
.github/workflows/benchmark.yml, .github/workflows/pyright.yml, .github/workflows/test.yml
All three CI workflows update their dependency installation commands to use openbabel>=3.2.0 instead of openbabel-wheel in the uv pip install step.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'build: replace openbabel-wheel with openbabel' directly and clearly summarizes the main change in the changeset, which is replacing the openbabel-wheel dependency with the official openbabel package across three workflow files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

Copy link
Copy Markdown

@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: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/pyright.yml:
- Line 16: The workflow's dependency install line uses a non-existent PyPI spec
`openbabel>=3.2.0`; update the run step string (the `run: uv pip install
--system -e .[amber,ase,pymatgen] rdkit 'openbabel>=3.2.0'` command) to use a
valid package spec such as `openbabel==3.1.1.1` (or `openbabel>=3.1.1.1,<3.2`)
so the installer can succeed, and apply the same change to the identical install
line in benchmark.yml if present.

In @.github/workflows/test.yml:
- Line 29: The workflow run step installs a non-existent package version
"openbabel>=3.2.0" causing CI installs to fail; update the pip install
invocation in the run step (the install command string) to a valid constraint
such as "openbabel>=3.1.1.1" or pin to "openbabel==3.1.1.1" (or remove the
openbabel spec if not required), then re-run the Python 3.10 and 3.13 test jobs
to confirm dependency installation succeeds.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 74df6d8c-65c3-45b9-bbb6-74da2bc682bd

📥 Commits

Reviewing files that changed from the base of the PR and between bc617b7 and e0de7b9.

📒 Files selected for processing (3)
  • .github/workflows/benchmark.yml
  • .github/workflows/pyright.yml
  • .github/workflows/test.yml

python-version: '3.12'
- run: pip install uv
- run: uv pip install --system -e .[amber,ase,pymatgen] rdkit openbabel-wheel
- run: uv pip install --system -e .[amber,ase,pymatgen] rdkit 'openbabel>=3.2.0'
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical | 🏗️ Heavy lift

Critical: Package version openbabel>=3.2.0 does not exist on PyPI.

This is the same issue as in benchmark.yml. The latest available openbabel version on PyPI is 3.1.1.1, which does not satisfy the >=3.2.0 constraint. The Pyright type-checking workflow will fail at dependency installation.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/pyright.yml at line 16, The workflow's dependency install
line uses a non-existent PyPI spec `openbabel>=3.2.0`; update the run step
string (the `run: uv pip install --system -e .[amber,ase,pymatgen] rdkit
'openbabel>=3.2.0'` command) to use a valid package spec such as
`openbabel==3.1.1.1` (or `openbabel>=3.1.1.1,<3.2`) so the installer can
succeed, and apply the same change to the identical install line in
benchmark.yml if present.

cache-suffix: "py${{ matrix.python-version }}"
- name: Install dependencies
run: uv pip install --system .[test,amber,ase,pymatgen] coverage ./tests/plugin rdkit openbabel-wheel
run: uv pip install --system .[test,amber,ase,pymatgen] coverage ./tests/plugin rdkit 'openbabel>=3.2.0'
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical | 🏗️ Heavy lift

Critical: Package version openbabel>=3.2.0 does not exist on PyPI.

This is the same blocking issue affecting all three workflows. The openbabel package latest version is 3.1.1.1, not 3.2.0 or higher. Both Python 3.10 and 3.13 test jobs will fail during dependency installation.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/test.yml at line 29, The workflow run step installs a
non-existent package version "openbabel>=3.2.0" causing CI installs to fail;
update the pip install invocation in the run step (the install command string)
to a valid constraint such as "openbabel>=3.1.1.1" or pin to
"openbabel==3.1.1.1" (or remove the openbabel spec if not required), then re-run
the Python 3.10 and 3.13 test jobs to confirm dependency installation succeeds.

@dosubot dosubot Bot added the lgtm This PR has been approved by a maintainer label May 27, 2026
@njzjz njzjz merged commit 46283e5 into deepmodeling:master May 27, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file lgtm This PR has been approved by a maintainer size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants